Adw Prd

Phase 4 — PRD

Produce 4-prd.md. This document defines what "done" looks like. A good PRD prevents scope creep during planning and gives the execution phase a clear target.

Inputs

• 1-phase-plan.md — task description and context
• 2-research.md — codebase findings, constraints, risks
• 0-state.md Notes — prototype findings if Phase 3 ran

Steps

1. Read the inputs listed above. The PRD reflects everything learned in research and (if applicable) the prototype. Do not re-research the codebase here.

2. Write 4-prd.md in .adw/<task-slug>/:

   # PRD: <task-slug>
   
   ## Goal
   <what success looks like; one paragraph tied directly to the task from 1-phase-plan.md>
   
   ## End state
   <concrete description of the system after the task is done; what a developer would
   observe when standing in front of the finished product>
   
   ## Acceptance criteria
   - AC-01: <specific, testable condition>
   - AC-02: <specific, testable condition>
   - ...
   
   ## Out of scope
   - <explicit list of things this task does not cover>