Twinned from https://github.com/cfsh/ninefold/issues/985 by tools/beads/import_github.py's reconcile pass.
Implement T7 from design_docs/008-live-status-for-design-doc-tasks.md (§8). No code dependency — can branch off main independently of T6. T3/T4/T5 are all merged now, so the interface and real examples to document already exist (design_docs/tools/operationalize_design.py, the 005b/006a/007 backfill PRs #942/#952/#957, dev.py designs PR #968).
Goal: the Issue-column authoring requirement and the "doc PR merges → immediate --apply follow-up PR" two-stage workflow are written down where a session doing a design round finds them.
Files:
- An addition to .claude/commands/design.md Step 6 (naming the follow-up --apply PR and pointing at operationalize_design.py) and Step 8 (the Issue-column requirement in the task-table template).
- A new notes/design-doc-tracking.md with the mechanics: issue title convention (<docid> T<n>: <title>), Project field values (Backlog/Ready/In Progress/Done/Deprioritized), the --dry-run/--apply/--close modes, and the mechanical-detection + liveness rules from design 008 §7. Link it from CLAUDE.md's notes/* index per that file's own "put it in notes/ and link it" rule.
Also add to Step 8's guidance directly (the generating rule design 008's own §8 follows, made findable for every future round): a task card's stated dependency must be the *real* one — what has to be merged or true for the task to be implementable — never "comes after task N in the build order." Sequencing preferences (real data to iterate against, narrative flow) are worth stating too, but separately, and never as a reason to nest one task's PR under another's unmerged branch. Reason: a session picking up any one task should be able to hold just that task's own card plus what's already on main, not the whole doc's accumulated diff — 008's own first draft confused these two axes before Aedan caught it.
Done when: Step 6 names the follow-up PR explicitly; Step 8's task table template includes the Issue column and the real-dependency-vs-sequencing-preference distinction; notes/design-doc-tracking.md exists and is linked from CLAUDE.md.
Refs: design_docs/008 §6/§8 · tracking #913 · T3 #931 (PR #937) · T4 #939 (PRs #942/#952/#957) · .claude/commands/design.md.
None.
No comments.