prd

Create, update, or list PRDs. Each PRD is a self-contained feature spec with status and priority.

Guardrails

• Do not implement code.
• Keep features "PRD-sized": one feature = one PRD.
• Split the feature if it spans >2 subsystems, >1 UI surface + backend, or >~1 day of work.
• Prefer asking a small number of high-value questions; otherwise write a draft PRD with explicit assumptions.
• Write the PRD so a junior dev (or another AI) can implement it without extra context.
• Use plain language, explicit edge cases, and verifiable acceptance criteria.
• Do not use Markdown tables (use checklists + bullets).
• When asking users for decisions, always provide numbered options with low-keystroke reply formats.
• Treat context capture as built-in.
• If durable decisions are made, update tasks/context.md in this step.
• Do not defer to a separate context pass.