product-speclisted

# Product Spec Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. Template: `.claude/docs/templates/product-spec.md`. Section by section: questions → section draft → edits → next. The file is written once at the end (or per section, the user's choice), always after "May I write?". ## Phase 1: Context Read `docs/specs/concept-brief.md` (if any), `technical-preferences.md`, `production/roadmap.md`. If the stack is not configured — suggest `/setup-stack` before or after (not blocking). ## Phase 2: Sections 1–10 Per section: 1–3 `AskUserQuestion`s → draft → "like this?". Non-functional requirements get the studio defaults (CWV, WCAG 2.2 AA, OWASP baseline) — the user confirms. Scope: insist on In/Later/Out; every Out item has a reason. ## Phase 3: Review Mode (`--review` or `production/review-mode.txt`, default `lean`): - `full`: `technical-director` (feasibility, stack risks) and `security-lead` (data, jurisdiction) in parallel via Task, verdict PASS/CONCERNS/FAIL with reasons. - `lean`: `technical-director` only if there are non-trivial NFRs/integrations. - `solo`: no review. CONCERNS/FAIL — show, propose edits, never advance the stage automatically. Then, for every BLOCKING and HIGH item of the verdict, one `AskUserQuestion`: record it in `production/findings.md` (template `findings.md`; id `ARCH-NNN`, severity, area/feature, the decision needed) (Recommended) · story stubs now via `/create-stor