What this skill does
Takes a raw feature idea (1 sentence or paragraph) and returns a PRD ready for a dev: problem, success metric, scope, edge cases, rollout plan. No PM jargon, written for whoever is going to implement it.
PRD structure
- Problem: the pain we're solving, with 1 user quote
- Hypothesis: why this feature solves the problem
- Success metric: 1 number, with baseline and target
- Scope: what's in and what is NOT
- Edge cases: 3-5 boundary situations already anticipated
- Risks: what can go wrong and the plan B
- Rollout: percent rollout, kill switch, owner
When to use
- Before opening a PR (aligns you with yourself)
- When the Linear/Jira ticket is vague
- To document it for a technical co-founder in another timezone
How it works
- You describe in 1-3 sentences what you want to do
- The skill asks 5 key questions (real problem, metric, edge cases)
- If you can't answer something, it flags what's left to investigate
- Generates the 1-page PRD, markdown format, ready to paste
- Suggests which questions are still worth answering before coding
Output example
PRD: Onboarding skip step
Problem
New users drop off at step 3 of onboarding (37% dropout).
Quote: "I just wanted to see the product, not fill all this in"
Success metric
Cut step 3 dropout from 37% to <20% in 30 days
Scope
- Add a "skip for now" button
- Reminder after 7 days to complete it
- NOT in scope: redesigning the whole onboarding
Edge cases
- User skips and comes back the same day: no reminder
- User skips and never comes back: reminder after 7d, then 30d, then never
- Mobile: the button cannot sit below the fold
Rollout
Feature flag, 10% → 50% → 100% in 1 week
Kill switch: env var ONBOARDING_SKIP_ENABLED
Owner: youPre-reqs
None.
