phased-plan

Phased plan

For any large feature or non-trivial refactor of codingest. Demand this skill when the user kicks off such work. Do not use standard plan mode (EnterPlanMode / ExitPlanMode) — this skill builds its own gated phased plan instead of the harness's generic plan.

Working dir: dev-docs/ (gitignored)

All plans, scratch, and intermediates live under dev-docs/ — gitignored local working state. The canonical layout + lifecycle is dev-docs/README.md — read it; it's the source of truth, this is just the phased-plan-relevant subset:

• This project's plan → dev-docs/plans/<slug>.md (durable).
• Design choices/trade-offs you weigh (parity/sync/algorithm) → dev-docs/designs/ (durable).
• Open threads → a lean one-line backlink in dev-docs/todos.md (detail in the linked durable doc, never inline).
• Offload large output to dev-docs/temp/ and report the path (>1-day purge) instead of printing it — stays under the response token gate.
• Parity/perf: harnesses → bench/scripts/, regression rows → bench/results/results.csv, heavy built graphs/dumps → bench/out/ (>14-day purge; never write artifacts next to the script). The committed regression record is PARITY.md + tests/parity.rs and BENCHMARKS.md.

Doctrine sync — first action of the run, before Phase −1

The estate's rules live in the sibling doctrine repo and are versioned. Pull them forward before planning anything, so a plan is never built on doctrine this repo has already been told is superseded.

1. Read ../doctrine/VERSION (a date serial, e.g. 2026.08.10) and dev-docs/.doctrine-synced. If the marker is absent, create it with the current version and note in the report-out that this was a first sync (there is nothing to replay — the marker's job starts now).
2. Versions equal → done. That is the normal case and it costs one file read; it is never worth skipping to save time, and "we're probably current" is not the check.
3. Doctrine ahead → read ../doctrine/CHANGELOG.md forward from the marker and act on every entry newer than it. Each item carries exactly one action class:
   • [skills-update] — merge the change into this repo's declared authority (per the Authority line at the top of AGENTS.md: the conventions file itself, and the tracked .agents/skills/ tree) and regenerate the adapters from it in the same action. Never hand-port into an adapter — that is what doctrine R7 measures.
   • [local-sweep] — run the check command the entry states. If it comes back clean, say so and move on. If it fails, the sweep becomes Phase 0 work of this plan — scoped, listed, and visible in the plan doc — never a silent side-task folded into an unrelated phase.
   • [info] — nothing to do.
4. Write the new version to dev-docs/.doctrine-synced only after those actions completed. A marker written first permanently hides the entry it skipped: the next run compares against it and sees nothing. If an entry could not be actioned, the marker advances only once that item is in the plan — the plan is the record, not the marker.