executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
prd-generatorGenerates a structured PRD from a feature description or brief. Use when asked to write, draft, or create a PRD.
Independent GitHub snapshot · Automated classification · Original documentation governs
When triggered, ask the user for:
Then generate a full PRD using the structure below.
What pain are we solving and for whom? Why does this matter now?
3-5 measurable outcomes we want to achieve with this feature. Format: "Increase [metric] by [amount] within [timeframe]"
What this feature explicitly will NOT do. Be specific. This section prevents scope creep.
Who uses this feature and in what context? Include 2-3 concrete scenarios (short narrative, not bullets).
Written as: "As a [user type], I want to [action] so that [outcome]." Group into: Must-have / Should-have / Nice-to-have
Written in Given/When/Then format for each must-have story. Should be specific enough that a QA engineer can write a test.
Two columns:
What must be decided before engineering starts? Format as questions, not statements. Assign an owner if known.
How will we measure whether this feature succeeded? Include leading indicators (early signals) and lagging indicators (final outcomes).
[ASSUMPTION][NEEDS INPUT]docs/prd.md