rulesets/.ai/workflows/spec-create.org, branch mainClaude Code skills, rules, and language bundles
https://git.cjennings.net/rulesets/atom?h=main2026-06-13T00:33:12+00:00feat(workflows): SUPERSEDED/CANCELLED decision states + old-model gate2026-06-13T00:33:12+00:00Craig Jenningsc@cjennings.net2026-06-13T00:33:12+00:00urn:sha1:22edacfd03de68eabd96d9aaa98a4dd5693535a6
A superseded decision now flips to SUPERSEDED (linking its replacement) and a moot one to CANCELLED. Both are done-class via a #+TODO: header the spec template auto-adds, so the [/] cookie counts them resolved and neither blocks implementation-ready. The TODO/DONE pair alone had lost the old State: field's superseded value.
spec-review's gate and Ready rubric now read "no decision is still TODO", and a spec still on the retired State: field model fails the gate item until converted. The gate as first written would have vacuously passed old specs, which have no decision tasks at all.
feat(workflows): spec decisions become org TODO/DONE tasks2026-06-13T00:15:15+00:00Craig Jenningsc@cjennings.net2026-06-13T00:15:15+00:00urn:sha1:7c052535f371c67956947a5afe711c71350feaf4
Each spec decision is now an org TODO task that flips to DONE when the decision-maker agrees, with a [/] cookie on the Decisions heading and a Discussion child for disputes. This replaces the inline State: proposed | accepted | superseded field. spec-response folds settled decisions by flipping them to DONE. spec-review's readiness gate and Ready rubric require the cookie to read complete. A spec can't move past draft to implementation-ready while any decision is still TODO.
From the .emacs.d handoff 2026-06-12.
feat(workflows): add spec-create, the author leg of the spec trio2026-06-09T22:11:49+00:00Craig Jenningsc@cjennings.net2026-06-09T22:11:49+00:00urn:sha1:1f0900281b8262539137bc1aff3f01cc05745139
spec-create is the front of the spec-create → spec-review → spec-response trio: the author writes a short design spec before non-trivial code, shaped to pass spec-review's readiness gate. It runs a when-to-spec proportionality gate first, then problem-first framing, design with forced alternatives and inline mini-ADR decisions, implementation phases with acceptance criteria and a readiness-dimensions menu, a terseness pass, and a hand-off self-check against the review rubric.