speclisted

# AI-Native SDLC Nine stages, each leaving a committed record the next begins by reading. That chain is the audit trail: ``` intent (issue | text | file) → spec delta → plan.md → diff + tests → PR + findings → incident → new intent ``` An intent is an **input**, not an artifact. It merges into one **living spec per product** at `.claude/productizer/spec.md`; the per-change record is the spec diff, joined to its issue by the branch name. Files are the only edit surface. Answer a short question in the session; publish a read-only **overview**, **fleet**, **spec**, **intake**, **backlog** or **band** view when someone wants to *look*, or the answer runs past six rows (`references/views.md`). **Never read anything back out of a view into the spec**: once a view is what people edit, the chain is no longer the audit trail. ## First: locate the work Find which stage this is and say so. The living spec always exists, so **file presence is not the state machine** — the issue and branch are. | State | Stage to run | |---|---| | no issue for this work | **1 · Plan** — capture the intent, open the issue | | issue open, spec unchanged for it | **2 · Design** — intake, then merge the delta | | spec delta merged, no branch | **3 · Build** — plan mode, `plan.md`, implement | | code changed, unverified | **4 · Test** — close the loop before a human looks | | change verified | **6 · Deploy** — review passes, gates, PR | | running in production | **9 · Maintain** — bands, diagnosis, ne