Repository navigation
docs: graduate plan-spec-kit-development-process to ADR-004 - #382
Merged
Merged
Conversation
All five phases landed via #380 and #381, so the plan graduates. ADR-004 records the decision rather than the document: each artifact owns exactly one kind of truth, and docs/development-process.md sequences the moves between them. The problem it solves is concrete -- one decision could plausibly live in spec.md, tasks.md, tasks/todo.md, a plan, an issue and a PR comment, so it gets written in several, updated in one, and the rest decay into confident contradictions. It records the two invariants that hold it together (intent is written before implementation, not reconstructed after it; work that will not finish on this branch leaves the branch), and that the process is scaled to the change, since a process with no skip rule gets skipped entirely. Negative consequences are recorded, including the honest one: the process is documented but not yet exercised here. This repository has not bootstrapped Spec Kit, so steps 1-3 are untested. That is #303. plans/ is now empty; its README says so explicitly rather than rendering an empty table. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Graduates the plan now that all five phases have landed (#380, #381), per the plan-lifecycle rule.
ADR-004
Records the decision rather than the document: each artifact owns exactly one kind of truth, and
docs/development-process.mdsequences the moves between them.The problem is concrete, not abstract — one decision could plausibly live in
spec.md,tasks.md,tasks/todo.md, a plan, an issue and a PR comment. Six homes, no rule about which is authoritative, so it gets written in several, updated in one, and the rest decay into confident contradictions.Two invariants hold it together: intent is written before implementation rather than reconstructed after it, and work that will not finish on this branch leaves the branch.
It also records why the process is scaled to the change — a process with no skip rule gets skipped entirely.
The honest consequence
ADR-004 states plainly that the process is documented but not yet exercised. This repository has not bootstrapped Spec Kit, so steps 1-3 are untested here. That is #303, which is next.
Also recorded as a negative: the sequence is a seventh process document and can itself go stale. The docs-link check verifies references resolve, not that guidance is still true.
Housekeeping
plans/is now empty. Its README says so explicitly rather than rendering an empty table with headers and no rows.tasks/todo.mdhas zero unchecked items and records the outcome of all three plan dispositions.Docs only — no behaviour change.
🤖 Generated with Claude Code