Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
Verify that an implementation matches the change artifacts (specs, tasks, design).
**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**
1. **If no change name provided, prompt for selection**
Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
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)".
**IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
2. **Check status to understand the schema**
```bash
openspec status --change "<name>" --json
```
Parse the JSON to understand:
- `schemaName`: The workflow being used (e.g., "spec-driven")
- `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context
- Which artifacts exist for this change
…
The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_bvzjizvpela33bpc
GET https://markdownregistry.com/api/v1/resolve?ref=rustyrazorblade/skills/openspec-verify-change
GET https://markdownregistry.com/api/v1/blob/336cd56a90854494373439f59d9cdd92d696a8cba97d5d8637865ba275c31c66
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
rustyrazorblade/skills · .claude/skills/openspec-apply-change/SKILL.md · Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or…
rustyrazorblade/skills · .claude/skills/openspec-archive-change/SKILL.md · Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after…
rustyrazorblade/skills · .claude/skills/openspec-bulk-archive-change/SKILL.md · Archive multiple completed changes at once. Use when archiving several parallel changes.
rustyrazorblade/skills · .claude/skills/openspec-explore/SKILL.md · Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use…
rustyrazorblade/skills · .claude/skills/openspec-onboard/SKILL.md · Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
rustyrazorblade/skills · .claude/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
rustyrazorblade/skills · .claude/skills/openspec-sync-specs/SKILL.md · Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta…
rustyrazorblade/skills · plugins/cassandra-expert/skills/data-model/SKILL.md · Data modeling and schema design for Apache Cassandra. Use when designing tables, choosing partition keys, modeling…
rustyrazorblade/skills · plugins/cassandra-expert/skills/token-skew/SKILL.md · Analyze token distribution and data ownership skew across Cassandra nodes and racks. Separates token placement quality…
fengshao1227/ccg-workflow · .agents/skills/openspec-verify-change/SKILL.md · Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete…
asymmetric-al/core · .agents/skills/openspec-verify-change/SKILL.md · Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is…
taskless/cli · .agents/skills/openspec-verify-change/SKILL.md · Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete…
intent-driven-dev/intent-driven-template · .opencode/skills/openspec-verify-change/SKILL.md · Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is…
yazelin/ching-tech-os · .claude/skills/openspec-verify-change/SKILL.md · Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete…
yazelin/ching-tech-os · .github/skills/openspec-verify-change/SKILL.md · Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete…
jim60105/copilot-prompt · skills/openspec-verify-change/SKILL.md · Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is…
