docs: document the one-PR-per-change archive convention - #22
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JJ7w12bnM5JqcDD7pEEqhQ
marandaneto
approved these changes
Jul 31, 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
3 participants
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.
Writes down the workflow rule that a change should land as one PR: once review approves the proposal, run apply + archive on the same branch, so the PR merges already archived — canonical spec synced, capability lists updated, archive-time tasks checked.
Until now the docs left this ambiguous and both patterns exist in history: #12 merged already archived, while #14 → #15 and #13 → #21 split propose and archive into two PRs. The split turned out to be a mistake — it leaves a merged proposal in a half-done state, invites review questions about unchecked archive-time task boxes (as happened on #13), and doubles the PR overhead for no benefit.
The rule goes in two places on purpose:
openspec/project.mdConventions — this file is injected into every AI-agent proposal/apply/archive run, so agents working in this repo will follow the one-PR flow automaticallyREADME.mdworkflow section — for human contributors🤖 Generated with Claude Code
https://claude.ai/code/session_01JJ7w12bnM5JqcDD7pEEqhQ
Generated by Claude Code