Track AI Plans

Use qing-plans/ as durable project memory: what the user wants, why the plan is shaped this way, what each stage changes, which modules are affected, what was observed and verified, and exactly what should happen next.

Preflight

1. Treat the Git top-level as ROOT. Set PLANCTL to this skill's own scripts/planctl.py and run every command as python3 "$PLANCTL" --root ROOT .... A repository holds plan data and dashboard.html only — never the runtime — so the same command works before the first plan exists and on every later machine.
2. If qing-plans/index.json exists, run validate, then resume. With no current plan, resume discovers one unfinished draft or lists draft candidates instead of silently ignoring them.
3. If only plans/index.json exists, it is V1 and read-only. Read references/migration.md before mutation.
4. If both directories exist, continue only when qing-plans/migration.json is verified; then qing-plans/ is authoritative and plans/ is legacy evidence.
5. A paused plan is current but never auto-resumed. Report it and ask the user before changing its lifecycle.

Route the request