work-plan

Write one work item per unit of work with permanent W-nn IDs, each carrying Depends on, Labels, Design sections, Scenarios, Size, and checkable acceptance criteria. Then run check-work-plan.py with --issues to emit a gh issue create script in wave order.

Declare Depends on for correctness ordering and Conflicts with for mechanical serialization per item, then run check-work-plan.py --write. It computes the waves and critical path from the dependency graph so parallelizable items are derived, not guessed.

A design is ready when its status is Accepted or partially implemented, no open questions change the item boundaries, section numbering is settled, a test plan with a scenario matrix exists, and external prerequisites are listed. Draft or Proposed designs should not be split.

Depends on means ordering is required for correctness, such as a reconciler needing a state graph first. Conflicts with means two items cannot be in flight simultaneously, like both editing the same types file and regenerating CRDs, but either may go first.

The checker rejects duplicate or unknown dependency IDs, dependency cycles, labels outside the repository's set, items missing acceptance criteria or descriptions, invalid sizes, and a hand-written section 1 that disagrees with the declared dependencies.

A filed plan becomes history: the issues carry status and the document records what was planned. Amend it with new IDs while items remain open, or supersede it with a phase-2 plan once its issues are closed; IDs are never reused or renumbered.