sdlc-implementlisted

# sdlc-implement **Executor resolution (host-aware):** - **Claude Code + `superpowers` installed** → prefer **`superpowers:test-driven-development`** + **`superpowers:executing-plans`** (their richer versions; where subagents exist, `superpowers:subagent-driven-development`). - **Otherwise** (Cursor / any host / no companion) → use this. Same discipline, portable. Two things happen in this phase: **build test-first**, and **execute the plan step by step**. ## Test-first (TDD) **No production code without a failing test first.** If you didn't watch the test fail, you don't know it tests the right thing. Wrote code before the test? Delete it and re-derive from the test. **Red → Green → Refactor**, one behavior at a time: 1. **RED** — write the smallest test for the next behavior. Run it. **Watch it fail for the right reason** (it asserts the behavior — not a typo or an import error). 2. **GREEN** — write the *minimal* code to pass. Run it. All green. 3. **REFACTOR** — clean up while staying green. "Clean up" is not a feeling; it is this list, and it is the same list `sdlc-review` axis 6 will judge by. Long Method, Large Class, Long Parameter List, Primitive Obsession (a unit doing too much) · Feature Envy, Inappropriate Intimacy, Message Chains, Middle Man (units too entangled) · Duplicate Code, Dead Code, Speculative Generality (code that should not exist). Fix it now, while the context is in your head and the diff is yours. Skip TDD only for throwaway