Phase 2 · PRD

Goal: a document precise enough for Claude to build from as autonomously as possible. Input: builder/01-idea.md. Output: builder/02-prd.md, with its flows mirrored into state.flows.

Read and follow:

• ${CLAUDE_PLUGIN_ROOT}/skills/_shared/tone.md
• ${CLAUDE_PLUGIN_ROOT}/skills/_shared/state-rules.md
• ${CLAUDE_PLUGIN_ROOT}/skills/_shared/gates.md: apply the PRD gate first.
• ${CLAUDE_PLUGIN_ROOT}/skills/prd/references/prompts.md (the method's original intent)

If the PRD has debt (it was generated by a gate), offer to review it first, as gates.md explains.

Step 1 · clarify

Set phases.prd.status to in_progress. Read 01-idea.md. Find what is still undefined, and ask about it in small batches:

• users and roles;
• the main things each user does;
• data (what is stored, how sensitive it is);
• rules and limits (e.g. "cancel up to 24 h before");
• edge cases (what if a slot is taken, what if there's no connection…);
• privacy, and tone and look.

Plan before writing: summarise what you understood in a short list and get a yes.

Step 2 · write

If the file already exists, follow "Existing outputs" in state-rules.md (revise it, never overwrite the user's edits). Otherwise: write builder/02-prd.md from ${CLAUDE_PLUGIN_ROOT}/skills/prd/templates/02-prd.md. Translate the section headings to the user's language. Keep these markers exactly, because other phases rely on them:

• each flow heading is ### F<n> — <name> (F1, F2…; the long dash —);
• each flow has an acceptance list. In English it is written Acceptance: with items of the form When <situation>, then <result>. In other languages, translate the words but keep the same structure.

Each flow is one thing a user does from start to finish ("Book a slot", "Cancel a booking"). Aim for 3–8 flows in a v1.

Mirror the flows into state.flows: { "id": "F1", "name", "acceptance": [...], "tasks": [], "validation": "pending" }. Set project.hasFrontend if it is still null.

Step 3 · review

Delegate the review to the prd-reviewer subagent (Agent tool, subagent_type: "builder:prd-reviewer", or prd-reviewer if that's how it's listed). Give it the paths of 01-idea.md and 02-prd.md. It returns a numbered list of proposed changes; it doesn't edit files.

Show the user the proposals in plain language and apply the ones they accept. If the user asked you to proceed with defaults, apply the ones marked "important". Make sure the "Design notes" section describes the user flows from the user's point of view.

If the subagent tool isn't available, do the review yourself, with the same checklist (${CLAUDE_PLUGIN_ROOT}/agents/prd-reviewer.md).

Step 4 · polish (optional)

Offer one more pass over the flows, looking for friction and confusing steps. Skip it (skipped) if the user declines or asked for defaults.

Finish

Check that:

• every flow has at least one acceptance criterion;
• state.flows matches the document;
• hasFrontend is true or false.

Ask the user to approve the PRD. Then:

• set review: reviewed and mark the phase done;
• set currentPhase to design, or to build if hasFrontend is false; in that case also set Design to not_applicable;
• update the progress page.

Close by suggesting /builder:next.