docs: drive the workflow by skill, not by CLI - #85
Merged
Conversation
CONTRIBUTING documented the four stages and left out how they are invoked, so eleven changes were assembled by driving the openspec CLI by hand. That skips the workflow the checks live in. Names both forms, states that each artifact has a template and rules retrievable with openspec instructions, and corrects the claim that archiving refuses to run with unchecked tasks. It warns and asks. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Thank you for contributing to this project! 😊🕹️ |
A blanket stage swept an incomplete change directory into a pull request about CONTRIBUTING. With only a proposal and no deltas it fails validation, which is the check working. It belongs in its own pull request once its artifacts exist. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CONTRIBUTING showed the four stages and left out how each is invoked, what the guards between them are, and that the artifacts have templates and rules. Every openspec CLI invocation is removed except init, which explains where the commands come from. AGENTS.md told agents to type slash commands they cannot reach, and said to follow the artifact build order rather than to let the skill write the artifacts at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The previous commit duplicated the skill table and the apply rules into AGENTS.md. Both apply to people as well, so both belong in CONTRIBUTING alone. What remains is the one thing that is genuinely agent-specific: the workflow names each step twice, and an agent cannot type a slash command, so it invokes the skill named for that step. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
retr0h
changed the title
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.
CONTRIBUTING documented the four stages and left out how each is invoked, what the guards between them are, and that the artifacts have templates and rules. Eleven changes were then assembled by driving the
openspecCLI by hand, which skips the workflow the guards live in.Every CLI invocation is gone
Only
openspec initremains, and only to explain where the/opsx:*commands come from. Removed: the--versioncheck in Setup, theopenspec updatemaintenance block, and two references that namedopenspec validatewherejust validateis what anyone actually runs.The workflow leads with how to invoke it
"Running a change" now opens with Invoke the skill, never the CLI and a table naming both forms of all six steps, with what each is for — not just what it is called. Every one of the twelve names is verified to resolve to a real file.
The numbered steps then say what each does and what it holds you to. Three things were missing entirely:
MODIFIEDdelta whose requirement heading does not exist in the corpus is reported there and nowhere else —just validatepasses it, because validation checks that a change is well formed, not that its deltas have somewhere to land. Suppressing the prompts suppresses that comparison too.AGENTS.md is a pointer again
It told agents to type
/opsx:propose— a slash command an agent cannot reach. Now it says the workflow names each step twice and an agent invokes the skill named for that step.An earlier revision of this branch duplicated the skill table and the apply rules into it. Both apply to people too, so both belong in CONTRIBUTING alone — the
repo-standardsrequirement is explicit thatAGENTS.mdcarries only what is specific to agents. Removed; the file is a line shorter than it started.just testpasses.🤖 Generated with Claude Code