PM Create PRD (Strict)
Current Phase
- •PRD (then AWAITING PRD APPROVAL)
Purpose
Turn a completed Discovery Summary into a production-ready PRD with zero ambiguity and a hard approval gate.
Paired Support Agents (recommended)
Before finalizing PRD content, proactively consult:
- •Senior Engineer for codebase/architecture feasibility checks.
- •Librarian for external documentation and platform constraints.
- •Smoke Test Planner output from discovery for testability and QA execution readiness.
Use their findings to reduce avoidable user clarification loops.
Inputs (required)
- •Discovery Summary (structured and complete)
- •Intended scope for this PRD
If Discovery Summary is incomplete, stop and ask only targeted clarification questions.
PRD Creation Rules
- •Propose slug format:
YYYY-MM-DD--kebab-slug. - •Create/update
docs/prd/<slug>.mdusingdocs/prd/_template.md. - •Ensure all required sections are filled.
- •Include
Open Questions. - •Do not request approval until
Open Questionsis empty. - •Include a smoke-test subsection covering happy path, unhappy path, regression, and post-implementation QA execution notes.
Approval Gate
- •Move to
Current phase: AWAITING PRD APPROVAL. - •Require exact user response:
approved. - •If user requests edits, apply edits and stay in approval phase.
Automatic Handoff to Beads Planning
When PRD is approved:
- •Automatically invoke:
- •
$pm-beads-plan Use PRD docs/prd/<slug>.md and treat PRD approval as confirmed
- •
- •Do not ask user to manually type the next command.
- •Preferred orchestration path: invoke via
spawn_agentand wait for completion.
Bootstrap (if missing)
Ensure:
- •
docs/prd/ - •
docs/prd/_template.md - •
docs/beads.md - •
AGENTS.md
Output Requirements (every run)
Always include:
- •
Current phase: PRDorCurrent phase: AWAITING PRD APPROVAL - •
PRD slug - •
PRD path - •
Open Questions status(must be empty before approval request) - •
What I need from you next
Invocation
- •Trigger strongly on
$pm-create-prd .... - •Also trigger on automatic handoff from
$pm-discovery.