implement-prd

You are orchestrating work for: $ARGUMENTS

Parse the arguments and pick a mode:

• --review-only present → Retrospective mode (arg is a PRD).
• --plan-only present → Plan-only mode (arg is a PRD).
• --execute present → Execute mode (arg is a PLAN file).
• otherwise → Pipeline mode (arg is a PRD).

You coordinate only — route all planning, coding, review, and testing through subagents to keep your context small.

Pipeline mode (fresh PRD implementation)

1. Plan — Invoke prd-planner on the PRD. Wait for the plan file path and status.

   • If STATUS: BLOCKED, surface the open questions to the user and STOP.

2. Execute → Review → Test loop — For each task in dependency order: a. Invoke prd-executor with the plan path and task name.

   • If BLOCKED, surface to the user and pause. b. Invoke prd-reviewer in task mode on the same task.
   • On REVIEW: CHANGES_REQUESTED, re-invoke prd-executor with the findings. Max 2 fix attempts, then escalate to the user. c. On REVIEW: APPROVED, invoke prd-tester on the task.
   • On TEST: FAIL, re-invoke prd-executor with the failure report, then re-run the reviewer ONLY if the fix touched files beyond the original task scope; otherwise go straight back to the tester. Max 2 fix attempts, then escalate. d. On TEST: PASS, proceed to the next task.

   Independent tasks (no shared files, no dependency edge) may execute in parallel; review and test steps still run per task.

3. Wrap up — When all tasks are DONE + APPROVED + PASS:

   • Run the full test suite once from the main session as a sanity check.
   • Summarize: tasks completed, files changed, tests added, review findings deferred (MINORs), anything flagged.
   • Suggest a commit message (do not commit unless asked).

Plan-only mode (--plan-only) — produce a plan and STOP

Nothing is implemented in this mode. Approval is not interactive; it lives in the plan file.

1. Pick the plan id <ID>: the ticket key in the PRD's title if it has one (e.g. PROJ-142), else the PRD file's basename. Invoke prd-planner on the PRD and tell it the exact output path: ./plans/<ID>.plan.md.
   • If STATUS: BLOCKED, surface the open questions and STOP.
2. Stamp it: ${CLAUDE_PLUGIN_ROOT}/scripts/plan-state.sh stamp ./plans/<ID>.plan.md <ID> (writes the header block, status: pending plus a hash of the plan, and adds an empty Progress section after a <!-- asdlc:progress --> line. The hash covers only what's above that line, so what a run logs there never voids the approval). Stamp adds that line itself and refuses a plan that already contains one, so the plan must not have it.
3. Tell the user the plan is written and awaiting approval. To approve: open the file, read the plan, and set status: approved in the header block — then run /asdlc:implement-prd ./plans/<ID>.plan.md --execute (/asdlc:jira-run also picks up approved plans for Jira tickets). STOP.