prd

1# /prd — Product Requirements Document Generator
2 
3## When to Use
4 
5**Don't use when:** architecture is already defined and you need implementation (use /architect then /archon); adding a small feature to an existing app (use /marshal directly).
6 
7- User describes an app or feature to build (greenfield or feature mode)
8- Before any Archon campaign for a new project or feature
9 
10## Mode Detection
11 
12Before starting, determine the mode:
13 
14**Greenfield mode**: No existing source files, or user explicitly says "new app" / "from scratch."
15Produces a full PRD as described below.
16 
17**Feature mode**: The project already has source files (check for `src/`, `app/`, `lib/`,
18`package.json` with dependencies, or similar). The user describes a feature to add, not a
19whole app ("add auth", "add a dashboard", "add payment processing").
20 
21In feature mode:
22- Read the existing file tree and `package.json`/equivalent before asking questions
23- The existing stack is a given — don't recommend alternatives
24- "Architecture" section describes integration points with existing code, not standalone shape
25- End conditions MUST include regression checks: "existing tests still pass", "typecheck has no new errors"
26- "Out of Scope" is relative to the feature, not the whole app
27- Technical Decisions only covers decisions the feature introduces (new dependencies, new patterns)
28 
29The PRD template below works for both modes. Feature mode just scopes it tighter.
30 
31## Protocol
32 
33### Step 1: UNDERSTAND
34…