aboutsummaryrefslogtreecommitdiff
path: root/review-code
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-06 07:32:53 -0500
committerCraig Jennings <c@cjennings.net>2026-06-06 07:32:53 -0500
commit255031a403fdfb4ea49938068399270121ed1975 (patch)
tree52ce09c168fe32262b78298958a7c3a0ea646ea7 /review-code
parent13816d00d6bf0f6d4a878c4cb5cd27ac03f3a9ea (diff)
downloadrulesets-255031a403fdfb4ea49938068399270121ed1975.tar.gz
rulesets-255031a403fdfb4ea49938068399270121ed1975.zip
feat(workflows): build implementation tasks on Ready in spec-response
I added Phase 6 to spec-response: once the author confirms a spec is Ready, file the full implementation-task breakdown in todo.org rather than leave a Ready spec nobody can act on. The phase creates one task per implementation phase, runs a completeness pass against every acceptance criterion and principle rule, marks :solo: only where the agent can build and verify end to end, collects the rest under a Manual-testing task, and defers outward-facing publish steps until the user confirms. This is the author-side complement to spec-review's Phase 6, which emits the drop-in task block. Review produces the block, response files the work.
Diffstat (limited to 'review-code')
0 files changed, 0 insertions, 0 deletions