openspec-workflow
Skill1 starsChanged 3 months agoMITView on GitHub
Use when: working in an OpenSpec-initialized repository, creating or changing an OpenSpec proposal, applying an approved OpenSpec plan, or archiving a completed OpenSpec change.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- cedaniel200/atlas-templatetheir own version, first seen Nov 1, 2026
- AVANT-ICONIC/gpt-webui-skillstheir own version, first seen Oct 13, 2026
- AVANT-ICONIC/skillstheir own version, first seen Oct 13, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- cedaniel200/atlas-template★ 3same name
- AVANT-ICONIC/gpt-webui-skills★ 0same name
- AVANT-ICONIC/skills★ 0same name
- thistleknot/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- blast-radiusSkill
- broSkill
- codebase-designSkill
- code-reviewSkill
- confluence-workflowSkill
- creating-a-pr-mrSkill
- defuddleSkill
- diagram-designSkill
- docxSkill
- domain-modelingSkill
- engineering-principlesSkill
- forgejo-cliSkill
- frontend-designSkill
- gh-cliSkill
- git-conventional-commitsSkill
- git-working-agreementSkill
- glab-cliSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- howSkill
- improve-codebase-architectureSkill
- jira-workflowSkill
- json-canvasSkill
- k8s-opsSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- pdfSkill
- pptxSkill
- prototypeSkill
- researchSkill
- setup-matt-pocock-skillsSkill
- skill-minerSkill
- technical-writingSkill
- theme-factorySkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- unslopSkill
- wayfinderSkill
- whySkill
- writing-for-agentsSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use OpenSpec only for substantive features, cross-cutting refactors, or changes whose requirements need explicit review.
- Very specific: line 16
Use /opsx:explore when requirements, affected areas, or the solution are unclear.
- Very specific: line 18
Use /opsx:propose <change-name> once the change has a clear outcome.
- Distinctive: line 19
Ensure the proposal covers the problem, requirements, affected canonical specifications, design decisions where needed, and executable …
- Distinctive: line 25
Treat the approved proposal, specification deltas, design, and tasks as the implementation contract.
- Distinctive: line 29
Keep the proposal and task status accurate when implementation changes the agreed scope.
- Very specific: line 34
Before /opsx:archive, complete all of the following:
- Distinctive: line 36
Run the relevant tests, linting, type checks, and OpenSpec validation.
- Distinctive: line 39
Update every affected canonical specification so it fully represents the implemented behavior, including changed requirements, scenarios, …
- Distinctive: line 42
Do not archive a change while its delta changes behavior that the canonical specifications omit or contradict.
- Very specific: line 47
Use openspec init or openspec update only after explicit user approval, because either command changes repository files.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OpenSpec Workflow
Use OpenSpec only for substantive features, cross-cutting refactors, or changes whose requirements need explicit review. Do not create an OpenSpec change for a small, localized fix unless the user requests it.
Explore And Propose
- Confirm that the repository contains
openspec/before using OpenSpec commands. - Use
/opsx:explorewhen requirements, affected areas, or the solution are unclear. Do not write implementation code during exploration. - Use
/opsx:propose <change-name>once the change has a clear outcome. - Ensure the proposal covers the problem, requirements, affected canonical specifications, design decisions where needed, and executable tasks.
- Present the proposal and wait for user approval before
/opsx:apply.
Apply
- Treat the approved proposal, specification deltas, design, and tasks as the implementation contract.
- Implement tasks incrementally and run the narrowest relevant validation after completing each independently testable behavior or invariant.
- Keep the proposal and task status accurate when implementation changes the agreed scope. Ask before materially changing the plan.
Archive
Before /opsx:archive, complete all of the following:
- Run the relevant tests, linting, type checks, and OpenSpec validation.
- Review each delta requirement and scenario against the canonical
openspec/specs/**specifications. - Update every affected canonical specification so it fully represents the implemented behavior, including changed requirements, scenarios, and cross-specification consequences.
- Do not archive a change while its delta changes behavior that the canonical specifications omit or contradict.
- Summarize the validation and canonical-specification updates, then ask the user to confirm archiving.
Use openspec init or openspec update only after explicit user approval,
because either command changes repository files.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.