dev-storylisted

# Dev Story Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. File writes and any mutation (git, deploy) happen only after an explicit "May I write?" / "Proceed?" → "yes", asked as an `AskUserQuestion` with the recommended action first and the real alternatives (coordination-rules, rule 7); delegated agents follow the same protocol. After the "write" answer: `touch .claude/.write-consent` (rule 7). ``` /create-stories → /dev-story (this) → /code-review → /story-done ``` ## Phase 1: Story Argument or `production/session-state/active.md` (`Task:`); none — ask. Status must be Ready/In Progress. No `production/sprints/sprint-*.md` covers this story while the backlog holds more than three Ready stories → say so before the plan question and include `/sprint-plan` in its options (Recommended for the first story of a fresh backlog): the sprint layer must not be reachable only by the owner's memory. ## Phase 2: Context (read everything before starting) **Architecture prerequisites first** — regardless of how the project entered `build` (brownfield projects start there with the architecture phase unwalked): `docs/architecture/threat-model.md` and `docs/architecture/test-strategy.md` must exist — the catalog marks both `required`. Either missing → `BLOCKED (architecture prerequisites unmet — run /threat-model | /test-setup first)`; name only the missing ones, never loop a question about it. Then read: th