sdlc-planlisted

# sdlc-plan **Executor resolution (host-aware):** - **Claude Code + `superpowers` installed** → prefer **`superpowers:writing-plans`** (its richer version). - **Otherwise** (Cursor / any host / no companion) → use this. Same discipline, portable. Write the plan **before touching code**, for a reader with **zero context and questionable taste** — spell out exactly what to do. DRY, YAGNI, TDD, frequent commits. Then hand it to `sdlc-plan-review`. ## 1. Scope check If the spec spans multiple independent subsystems, split it into **separate plans** — one per subsystem, each producing working, testable software on its own. ## 2. File structure (decide decomposition first) Map which files are **created / modified** and each one's single responsibility. Small, focused files; files that change together live together (split by responsibility, not by layer); **follow the codebase's existing patterns** — don't unilaterally restructure. ## 3. Tasks — right-sized + bite-sized - A **task** is the smallest unit that carries its own test cycle and is worth a reviewer's gate; it ends with an **independently testable deliverable**. Fold setup/config/docs into the task that needs them; split only where a reviewer could reject one and approve its neighbor. - Each **step** is one action (~2–5 min): *write the failing test → run it, watch it fail → minimal code to pass → run, green → commit.* ## 4. Definition of done State, per task and for the whole plan, the **checkable condition** t