implementlisted

# Implement Build the work — but first agree **how much process** it deserves. A throwaway prototype and a production feature run the same skill; they differ only in which **phases** are on. The run plan is proposed once, tuned by the user, then executed predictably. The Jira project / Confluence space keys come from memory when tracking is on; read them, don't ask (`reference_jira_default_project.md`, `reference_confluence_default_space.md`). ## The pipeline Five phases. Each can be **on**, **off**, or **tuned**: 1. **Source** — where the work is defined: a Jira ticket, a `/plan-to-spec` page, or free-form from the conversation. 2. **Test-first** — drive `/tdd` (red → green) at pre-agreed seams. *Off* = build directly, no tests. 3. **Verify** — typecheck + run tests (single files during, full suite at end). *Off* = no test/type setup to run. 4. **Review** — `/code-review` (Standards + Spec axes) of the working diff. *Off* = skip review. 5. **Track** — commit; open an MR; move the ticket. Tunable down to *commit only*, or *nothing* (prototype). ## Step 1 — Propose the run plan Before building anything, **detect a preset** from the context and present the run plan as an editable list. The user edits any line or names a preset; you don't build until they approve. **Presets:** | Preset | Test-first | Verify | Review | Track | | :--- | :--- | :--- | :--- | :--- | | `prototype` | off | off | off | nothing (or commit only) | | `standard` | at key seams | typecheck + tests