diff options
| author | Jesse Vincent <jesse@primeradiant.com> | 2026-09-26 14:12:30 -0700 |
|---|---|---|
| committer | Jesse Vincent <jesse@primeradiant.com> | 2026-09-26 14:12:30 -0700 |
| commit | c39e55816498f48112a60242309df0d1cbbc5d9a (patch) | |
| tree | 532d6e24a90474d7eda10591b132cc4abffc0891 | |
| parent | 8ecf3bb20d63487eb2319ea793a89c7a7e7e0258 (diff) | |
Executors tick a completed task's plan checkboxesfeat/executors-tick-plan-checkboxes
The writing-plans header promises checkbox tracking, but neither
executor ticked the boxes, so a finished plan looked untouched once
the workspace ledger was cleaned up (#1075). Draft: needs evals.
| -rw-r--r-- | skills/executing-plans/SKILL.md | 9 | ||||
| -rw-r--r-- | skills/subagent-driven-development/SKILL.md | 13 |
2 files changed, 12 insertions, 10 deletions
diff --git a/skills/executing-plans/SKILL.md b/skills/executing-plans/SKILL.md index 49077ad..0ce10a1 100644 --- a/skills/executing-plans/SKILL.md +++ b/skills/executing-plans/SKILL.md @@ -77,7 +77,7 @@ digraph process { "Plan wrong? Rule and ledger. Code wrong? systematic-debugging" [shape=box]; "Commit as the plan's commit steps say" [shape=box]; "Completion contract met?" [shape=diamond]; - "task-done: run tests, ledger the result; mark todo complete" [shape=box]; + "task-done: run tests, ledger the result; tick plan boxes, mark todo complete" [shape=box]; } "Setup: worktree, workspace + ledger, read plan + spec, pre-flight scan" [shape=box]; @@ -95,8 +95,8 @@ digraph process { "Step output matches plan's Expected?" -> "Commit as the plan's commit steps say" [label="yes, last step"]; "Commit as the plan's commit steps say" -> "Completion contract met?"; "Completion contract met?" -> "Work the steps in order: TDD, run every verification, read every output" [label="no - finish the task"]; - "Completion contract met?" -> "task-done: run tests, ledger the result; mark todo complete" [label="yes"]; - "task-done: run tests, ledger the result; mark todo complete" -> "More tasks remain?"; + "Completion contract met?" -> "task-done: run tests, ledger the result; tick plan boxes, mark todo complete" [label="yes"]; + "task-done: run tests, ledger the result; tick plan boxes, mark todo complete" -> "More tasks remain?"; "More tasks remain?" -> "task-start: brief + BASE; read the brief" [label="yes"]; "More tasks remain?" -> "Final whole-branch review (fresh reviewer if you have one)" [label="no"]; "Final whole-branch review (fresh reviewer if you have one)" -> "Re-grade, then: Critical/Important → ONE fix pass, each fix RED→GREEN + green suite; Minor → ledger"; @@ -229,7 +229,8 @@ if they pass — appends the completion line to the ledger: `Task <N>: complete (commits <base7>..<head7>, tests: <command> → <result>)` A failing run records nothing; the task is not complete. When it records, -mark the todo complete and take the next task. +tick the task's boxes in the plan (`- [ ]` → `- [x]`), mark the todo +complete, and take the next task. ## Final Review diff --git a/skills/subagent-driven-development/SKILL.md b/skills/subagent-driven-development/SKILL.md index f7bbf6a..4da1d34 100644 --- a/skills/subagent-driven-development/SKILL.md +++ b/skills/subagent-driven-development/SKILL.md @@ -80,7 +80,7 @@ digraph process { "Any load-bearing finding?" [shape=diamond]; "Rule and continue; stop only if every path forward is a guess" [shape=box]; "Park findings in ledger with rulings" [shape=box]; - "Append completion to ledger, mark todo complete" [shape=box]; + "Append completion to ledger, tick plan boxes, mark todo complete" [shape=box]; } "Setup: worktree, ledger check, read plan, pre-flight review" [shape=box]; @@ -97,22 +97,22 @@ digraph process { "Implementer asks questions?" -> "Implementer implements, tests, commits, self-reviews" [label="no"]; "Implementer implements, tests, commits, self-reviews" -> "Generate review package, dispatch task reviewer (./task-reviewer-prompt.md)"; "Generate review package, dispatch task reviewer (./task-reviewer-prompt.md)" -> "Spec ✅ and quality approved?"; - "Spec ✅ and quality approved?" -> "Append completion to ledger, mark todo complete" [label="yes"]; + "Spec ✅ and quality approved?" -> "Append completion to ledger, tick plan boxes, mark todo complete" [label="yes"]; "Spec ✅ and quality approved?" -> "Finding conflicts with plan text?" [label="no"]; "Finding conflicts with plan text?" -> "Rule on the conflict, ledger the ruling" [label="yes"]; "Rule on the conflict, ledger the ruling" -> "Fix round R of 5: R≤3 resume implementer; R≥4 fresh implementer, more capable model"; "Finding conflicts with plan text?" -> "Fix round R of 5: R≤3 resume implementer; R≥4 fresh implementer, more capable model" [label="no"]; "Fix round R of 5: R≤3 resume implementer; R≥4 fresh implementer, more capable model" -> "Dispatch scoped re-review (./re-review-prompt.md)"; "Dispatch scoped re-review (./re-review-prompt.md)" -> "All findings addressed?"; - "All findings addressed?" -> "Append completion to ledger, mark todo complete" [label="yes"]; + "All findings addressed?" -> "Append completion to ledger, tick plan boxes, mark todo complete" [label="yes"]; "All findings addressed?" -> "R = 5?" [label="no"]; "R = 5?" -> "Fix round R of 5: R≤3 resume implementer; R≥4 fresh implementer, more capable model" [label="no - next round"]; "R = 5?" -> "Adjudicate each open finding" [label="yes - breaker trips"]; "Adjudicate each open finding" -> "Any load-bearing finding?"; "Any load-bearing finding?" -> "Rule and continue; stop only if every path forward is a guess" [label="yes"]; "Any load-bearing finding?" -> "Park findings in ledger with rulings" [label="no"]; - "Park findings in ledger with rulings" -> "Append completion to ledger, mark todo complete"; - "Append completion to ledger, mark todo complete" -> "More tasks remain?"; + "Park findings in ledger with rulings" -> "Append completion to ledger, tick plan boxes, mark todo complete"; + "Append completion to ledger, tick plan boxes, mark todo complete" -> "More tasks remain?"; "More tasks remain?" -> "Dispatch implementer subagent (./implementer-prompt.md)" [label="yes"]; "More tasks remain?" -> "Dispatch final code reviewer (../requesting-code-review/code-reviewer.md)" [label="no"]; "Dispatch final code reviewer (../requesting-code-review/code-reviewer.md)" -> "Final findings? ONE fix dispatch, one scoped re-review, adjudicate residuals"; @@ -438,7 +438,8 @@ message as your other bookkeeping: - `Task <N>: complete (commits <base7>..<head7>, <K> parked)` after a tripped breaker -Then mark the todo complete and move on. Never move to the next task while +Then tick the task's boxes in the plan (`- [ ]` → `- [x]`), mark the todo +complete, and move on. Never move to the next task while the review has open Critical/Important issues that are neither fixed nor parked-with-ruling at the cap. |
