requirement-definitionlisted

## Inputs - `state.json` → `phase: "new"` or `"requirements_sprint"` - `docs/product/brief.md` — the human-authored product brief, co-authored at launch in **both** human and agent modes (via the `create-brief` skill: the `scrum-start.sh` pre-flight on a new project, or `--brief <file>` in autonomous mode). It is the **anchor** for the interview and the source of truth for in-scope vs out-of-scope. Requirements must realize the brief; where they conflict, exactly one side is amended (see step 6). On the rare path where no brief exists (user skipped the pre-flight, or a pre-brief resumed project), the ceremony proceeds from the interview alone and the brief is treated as absent. ## Outputs - `docs/requirements.md` — business, functional, non-functional requirements (committed to repo) - `docs/product/brief.md` — **possibly amended** during step 6 reconciliation when the interview reveals the brief was wrong/stale (committed to repo) - `docs/requirements-benchmark.md` — benchmark findings from similar products / prior art (source URLs + per-item `adopt`/`adapt`/`reject` disposition), gathered via mandatory web search (committed to repo) - `CLAUDE.md` — project root, ~200 lines target (project overview + cautions). Created if missing; existing→user choice - `state.json` → new→requirements_sprint→backlog_created - `backlog.json` — initial coarse-grained PBIs + `next_pbi_id` ## Preconditions - state.json phase: "new" or "requirements_sprint" - No existing requ