docs: document the OpenSpec change flow, point agents at it - #35
Merged
Conversation
dtump
force-pushed
the
docs/openspec-workflow
branch
from
August 25, 2026 07:03
3c33d9e to
7de2a47
Compare
Spell out when a change is required and the propose → apply → validate → archive → PR order, so the flow is not inferred from existing changes.
dtump
force-pushed
the
docs/openspec-workflow
branch
from
August 25, 2026 07:03
7de2a47 to
c738788
Compare
AGENTS.md carries the pointer and the few rules agents miss most; CLAUDE.md is a one-line redirect to it rather than a second copy that can drift.
dtump
force-pushed
the
docs/openspec-workflow
branch
from
August 25, 2026 07:17
df38688 to
2ed1d4d
Compare
sbp-bvanb
approved these changes
Aug 25, 2026
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
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.
Adds an
OpenSpec changesheading to CONTRIBUTING.md: when a change needs one (behaviour or spec impact — not small fixes that leave the specs alone) and the order to do it in — draft, apply, validate, archive, then open the PR — with the/opsx:*command or CLI equivalent for each step. Also states thatopenspec/specs/is generated by the archive step and must not be hand-edited, and that artifacts for a far-reaching change are worth reviewing before implementation starts.Adds
AGENTS.mdpointing coding agents at that section plus the few rules they miss most, withCLAUDE.mdas a one-line redirect rather than a second copy. Verifiedopenspec initleaves both files untouched — it writes per-tool skill directories, not a managed block in root instruction files.Docs only, no spec impact, so no OpenSpec change of its own.