planlisted

# Plan Create a structured multi-step implementation plan in `.context/plans/` before coding starts. This skill is the single-purpose entry point for **planning**; the formatting canon lives in the shared `conventions` reference package (not forked here). ## Triage — pick the mode before anything else Runs on **every** invocation, before Step 0. Skip it in one line only when the user names the mode outright ("plan this as scoped", "/aidex:plan full"). Canon: `plan-conventions.md` §Plan mode. The discriminator is **not size** — it is whether more than one viable design exists and whether choosing wrong is expensive. Delegate the investigation to a **subagent** (`Explore` or `general-purpose`, `model-policy: inherit-session` — a repo read at the session's own depth, deliberately not pinned): it may read as much of the repo as it needs, but its output contract is fixed — the five signals with their evidence, plus one recommended outcome. No design sketches, no architectural alternatives. If it cannot decide from what it read, the outcome is already `research`. | Observable | If yes | |---|---| | An existing repo pattern this change repeats | scoped | | Touches a shared contract, or an API another module consumes | full | | Requires a migration or schema change | full | | Reverts with a single `git revert` | scoped | | Two or more viable designs where choosing wrong costs a rewrite | full | Present the **evidence per signal**, then the recommendation — a bare verdict invite