openspec-verify-change
Skill1 starsChanged 2 days agoApache-2.0View on GitHub
Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".
81 other projects use a version of this, 76 of them edited.
Adopted by
Most recently taken up by
- cylingo-group/claw-installeredited, first seen Nov 15, 2026
- haskelium/openprezedited, first seen Nov 15, 2026
- rulemason/rulemasonedited, first seen Nov 15, 2026
- Azure/azclipsedited, first seen Nov 15, 2026
- ValorVie/custom-skillsedited, first seen Nov 8, 2026
- FuDesign2008/open-skillsedited, first seen Nov 6, 2026
Used with
Projects with it also use draft-openspec-docs, release-openspec and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
goernSkilldraft-openspec-docs
Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.
Also in 3 projects that use this
goernSkillrelease-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is complete, what the next release step is, or to continue a release paused for human approval.
Also in 3 projects that use this
SentrySkillcode-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
Also in 3 projects that use this
GitHubSkillprd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
Also in 3 projects that use this
OpenAISkillrequesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Also in 3 projects that use this
OpenAISkillexecuting-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Also in 3 projects that use this
- +2 more from goern
Other versions81 projects use a version of this.
Word for word · 1
- arabold/docs-mcp-server★ 1.8k100% same
Edited · 76
- Fission-AI/OpenSpec★ 75k37% same
- alibaba/druid★ 28k85% same
- PBH-BTN/PeerBanHelper★ 6.4k85% same
- fengshao1227/ccg-workflow★ 6k85% same
- owncloud/android★ 4.2k97% same
- Soju06/codex-lb★ 3.3k85% same
- Draculabo/AntigravityManager★ 2.5k85% same
- arkflow-rs/arkflow★ 1.3k87% same
- jamro/tiny-engineer★ 1.2k39% same
- microsoft/rayfin★ 64684% same
66 more not listed
Wrote their own version · 4
- studyzy/imewlconverter★ 10ksame name
- studyzy/OpenSpec-cn★ 1.3ksame name
- charliehzm/medharness★ 85same name
- redhat-developer/rhdh-skills★ 20same 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
39 rules. 33 are common, 2 are distinctive, and 4 are very specific to this project.
33
Common
Most of the 78 edited versions we read keep these.
2
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
- Common: line 13
Verify that an implementation matches the change artifacts (specs, tasks, design).
- Distinctive: line 34
If a name is provided, use it.
- Very specific: line 37
If ambiguous, run openspec list --json to get available changes and ask the user to select one
- Distinctive: line 39
When prompting, show changes that have implementation tasks (tasks artifact exists).
- Very specific: line 43
Always announce: "Using change: <name>" and how to override (e.g., /opsx:verify <other>).
- Common: line 64
Create a report structure with three dimensions:
- Very specific: line 74
If contextFiles.tasks exists, read every file path in it
- Common: line 79
If incomplete tasks exist:
- Common: line 80
Add CRITICAL issue for each incomplete task
- Very specific: line 84
If delta specs exist in contextFiles.specs:
- Common: line 87
Search codebase for keywords related to the requirement
- Common: line 89
If requirements appear unimplemented:
- Common: line 90
Add CRITICAL issue: "Requirement not found: <requirement name>"
- Common: line 97
Search codebase for implementation evidence
- Common: line 98
If found, note file paths and line ranges
- Common: line 101
Add WARNING: "Implementation may diverge from spec: <details>"
- Common: line 106
Check if conditions are handled in code
- Common: line 107
Check if tests exist covering the scenario
- Common: line 108
If scenario appears uncovered:
- Common: line 109
Add WARNING: "Scenario not covered: <scenario name>"
- Common: line 117
Verify implementation follows those decisions
- Common: line 119
Add WARNING: "Design decision not followed: <decision>"
- Common: line 121
If no design.md: Skip design adherence check, note "No design.md to verify against"
- Common: line 125
Check file naming, directory structure, coding style
- Common: line 126
If significant deviations found:
- Common: line 127
Add SUGGESTION: "Code pattern deviation: <details>"
- Common: line 162
If CRITICAL issues: "X critical issue(s) found.
- Common: line 163
If only warnings: "No critical issues.
- Common: line 164
If all clear: "All checks passed.
- Common: line 169
Correctness: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
- Common: line 170
Coherence: Look for glaring inconsistencies, don't nitpick style
- Common: line 171
False Positives: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
- Common: line 172
Actionability: Every issue must have a specific recommendation with file/line references where applicable
- Common: line 176
If only tasks.md exists: verify task completion only, skip spec/design checks
- Common: line 177
If tasks + specs exist: verify completeness and correctness, skip design
- Common: line 178
If full artifacts: verify all three dimensions
- Common: line 179
Always note which checks were skipped and why
- Common: line 183
Use clear markdown with:
- Common: line 188
No vague suggestions like "consider reviewing"
“Common” is measured: kept by at least 6 in 10 of the 78 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
Verify that an implementation matches the change artifacts (specs, tasks, design).
Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context, schemas, view). Once selected, treat --store <id> as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "<name>" --json --store "<id>", not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.
Project check: These steps expect a project that already uses OpenSpec. Before the first step that writes anything (new change, archive, sync specs, or authoring an artifact file), confirm the project has a root: run openspec list --json (with --store <id> when a store is selected, since the store is then the root) and read root. A root object means the project is set up. "root": null means it is not - there is no openspec/ directory here, and a write such as openspec new change would create one as a side effect. The command also exits non-zero, which is that answer rather than a broken CLI, so read the JSON instead of retrying or working around it.
One "root": null is not about setup: when a status error message starts with Declared in or Invalid store declaration in and names this project's openspec/config.yaml (or config.yml), the project does use OpenSpec through a store it declares, which this machine cannot resolve (the store is not registered, or the store: line is malformed). Do not treat it as uninitialized and skip the branches below: stop before writing and show the user that error's message and fix.
Otherwise, with no root, what happens next depends on how this workflow was reached:
- Auto-selected: you chose this workflow yourself, without the user naming OpenSpec, naming this skill, or running its slash command. Stop using OpenSpec and answer the request normally, as you would with no OpenSpec installed. Do not ask them to set anything up and do not mention OpenSpec setup.
- Explicit OpenSpec request: the user named OpenSpec, named this skill, or ran its slash command. Stop before writing and ask how to proceed: set this project up (
openspec init), target a store they already have (--store <id>), or continue without OpenSpec for this request. Wait for their answer.
In both branches, never create the root as a side effect: do not run openspec init until the user asks for it, do not hand-create openspec/ files, and do not let a command create it.
Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
Steps
Select the change
If a name is provided, use it. Otherwise:
- Infer from conversation context if the user mentioned a change
- Auto-select if only one active change exists
- If ambiguous, run
openspec list --jsonto get available changes and ask the user to select one
When prompting, show changes that have implementation tasks (tasks artifact exists). Include the schema used for each change if available. Mark changes with incomplete tasks as "(In Progress)".
Always announce: "Using change:
<name>" and how to override (e.g.,/opsx:verify <other>).- Check status to understand the schema
Parse the JSON to understand:openspec status --change "<name>" --jsonschemaName: The workflow being used (e.g., "spec-driven")planningHome,changeRoot,artifactPaths, andactionContext: path and scope context- Which artifacts exist for this change
Get planning context and load artifacts
openspec instructions apply --change "<name>" --jsonThis returns the change directory and
contextFiles(artifact ID -> array of concrete file paths). Read all available artifacts fromcontextFiles.Initialize verification report structure
Create a report structure with three dimensions:
- Completeness: Track tasks and spec coverage
- Correctness: Track requirement implementation and scenario coverage
- Coherence: Track design adherence and pattern consistency
Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
Verify Completeness
Task Completion:
- If
contextFiles.tasksexists, read every file path in it - Parse checkboxes: complete means the box holds only
x/X, ignoring spacing (- [ x]is complete); every other marker is incomplete (- [ ],- [], and unfamiliar ones such as- [~]or- [-]) - Count complete vs total tasks
- If incomplete tasks exist:
- Add CRITICAL issue for each incomplete task
- Recommendation: "Complete task:
<description>" or "Mark as done if already implemented"
Spec Coverage:
- If delta specs exist in
contextFiles.specs:- Extract all requirements (marked with "### Requirement:")
- For each requirement:
- Search codebase for keywords related to the requirement
- Assess if implementation likely exists
- If requirements appear unimplemented:
- Add CRITICAL issue: "Requirement not found:
<requirement name>" - Recommendation: "Implement requirement X:
<description>"
- Add CRITICAL issue: "Requirement not found:
- If
Verify Correctness
Requirement Implementation Mapping:
- For each requirement from delta specs:
- Search codebase for implementation evidence
- If found, note file paths and line ranges
- Assess if implementation matches requirement intent
- If divergence detected:
- Add WARNING: "Implementation may diverge from spec:
<details>" - Recommendation: "Review
<file>:<lines>against requirement X"
- Add WARNING: "Implementation may diverge from spec:
Scenario Coverage:
- For each scenario in delta specs (marked with "#### Scenario:"):
- Check if conditions are handled in code
- Check if tests exist covering the scenario
- If scenario appears uncovered:
- Add WARNING: "Scenario not covered:
<scenario name>" - Recommendation: "Add test or implementation for scenario:
<description>"
- Add WARNING: "Scenario not covered:
- For each requirement from delta specs:
Verify Coherence
Design Adherence:
- If
contextFiles.designexists:- Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
- Verify implementation follows those decisions
- If contradiction detected:
- Add WARNING: "Design decision not followed:
<decision>" - Recommendation: "Update implementation or revise design.md to match reality"
- Add WARNING: "Design decision not followed:
- If no design.md: Skip design adherence check, note "No design.md to verify against"
Code Pattern Consistency:
- Review new code for consistency with project patterns
- Check file naming, directory structure, coding style
- If significant deviations found:
- Add SUGGESTION: "Code pattern deviation:
<details>" - Recommendation: "Consider following project pattern:
<example>"
- Add SUGGESTION: "Code pattern deviation:
- If
Generate Verification Report
Summary Scorecard:
## Verification Report: <change-name> ### Summary | Dimension | Status | |--------------|------------------| | Completeness | X/Y tasks, N reqs| | Correctness | M/N reqs covered | | Coherence | Followed/Issues |Issues by Priority:
- CRITICAL (Must fix before archive):
- Incomplete tasks
- Missing requirement implementations
- Each with specific, actionable recommendation
- WARNING (Should fix):
- Spec/design divergences
- Missing scenario coverage
- Each with specific recommendation
- SUGGESTION (Nice to fix):
- Pattern inconsistencies
- Minor improvements
- Each with specific recommendation
Final Assessment:
- If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
- If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
- If all clear: "All checks passed. Ready for archive."
- CRITICAL (Must fix before archive):
Verification Heuristics
- Completeness: Focus on objective checklist items (checkboxes, requirements list)
- Correctness: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
- Coherence: Look for glaring inconsistencies, don't nitpick style
- False Positives: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
- Actionability: Every issue must have a specific recommendation with file/line references where applicable
Graceful Degradation
- If only tasks.md exists: verify task completion only, skip spec/design checks
- If tasks + specs exist: verify completeness and correctness, skip design
- If full artifacts: verify all three dimensions
- Always note which checks were skipped and why
Output Format
Use clear markdown with:
- Table for summary scorecard
- Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
- Code references in format:
file.ts:123 - Specific, actionable recommendations
- No vague suggestions like "consider reviewing"
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.

