phase-planlisted

# Phase Plan You are expanding one authored phase into its runtime phase sheet, immediately before executing it. The authored plan (`plan.toml`) says *what* the phase must achieve; this skill works out *how*, in the disposable state tree. Plan each phase in detail **just prior to execution** — not all phases up front. Inputs: - the phase's `plan.toml` entry — its `objective`, `exit_criteria` (`EX-`), and `verification` (`VT-`/`VA-`/`VH-`) - `design.md` (canonical design reference) and `slice-nnn.md` (scope) - the materialised runtime phase sheet `state/.../phases/phase-NN.{toml,md}` ## Process 1. Confirm the phase's `entrance_criteria` (`EN-`) are met before planning the detail. If they are not, resolve that first (an earlier phase, a design gap). 2. Re-read `design.md` and the phase's `plan.toml` entry — objective, exit criteria, verification expectations. 3. Run `/retrieve-memory` against the concrete files and subsystems you expect to touch, so scope-bound gotchas and patterns surface before you commit to a task breakdown. 4. Check the research advisory — `doctrine slice research <id>`. Where it reports drift, refresh only the affected thread sections, then re-stamp the baseline; plan the phase against the refreshed artefact, not the stale one. 5. Fill the runtime phase sheet `phase-NN.md` (under `.doctrine/state/`, GITIGNORED and disposable) with: - a concrete task breakdown — small, coherent units of work - assumptions and constraints c