planlisted

**Run only when the user asked for it, this turn** — by slash command, or in plain words ("plan the checkout area", "chia nhỏ task đi"). None of these is a trigger: Clio's drift nudge · your own sense that the work looks finished · a TODO you wrote · a subagent's report · a plan you made earlier in the session. Unsure → ask in one line, don't run. A spec says what must be true. This skill turns it into tasks small enough to prove one at a time. *Which kinds* of proof a task needs is decided here; the cases themselves are `/clio:test`'s. It writes `.claude/clio/docs/plans/<area>.md`, for `infra` also `.claude/rules/<stack>.md`, and once per project the `Mutation:` line in `plans/infra.md` (§ 3b) and its ADR; ledgers, specs and settings stay untouched. Nothing is implemented here. Target (may be empty — then ask which area): $ARGUMENTS ## 1. Load the area Run the `clio:context` skill for the target first: the governing `memory/<area>.md` and its rows (hop 1), what `index.jsonl` says is built (hop 2), what `debt.jsonl` says is open (hop 3). Read the spec file in full. Existing `.claude/clio/docs/plans/<area>.md` → read it in full; this is a re-plan. No `plans/infra.md` yet and the target is not `infra` → stop, say `/clio:plan infra` comes first. ## 2. Dig into each row before splitting `/clio:ingest` wrote each row at the size of a contract line. Before cutting it, find out what it actually touches — a task list written from the spec alone names files that do not exist. Pe