openspec-verify
OpenSpec Verify Skill
Use /opsx:verify to validate that the implementation matches the change artifacts. Checks three dimensions — completeness, correctness, and coherence — and reports issues categorized as CRITICAL, WARNING, or SUGGESTION.
When to Use
- After implementing tasks with openspec-apply, before archiving.
- The user says "verify", "check my work", "validate implementation".
- Quality gate before archiving a change.
Prerequisites
- Tasks implemented (via openspec-apply or manual coding).
Workflow
- Run verification
/opsx:verify— verify the current/inferred change./opsx:verify <change-name>— verify a specific change.
More from partme-ai/openspec-skills
openspec-explore
Think through ideas, investigate problems, and clarify requirements before committing to a change using `/opsx:explore`. Use when the user says "explore an idea", "think through this", "investigate options", or wants to brainstorm before creating a formal change.
50openspec-apply
Implement tasks from the change using `/opsx:apply`, working through the task list and checking off items. Use when the user says "implement", "apply the change", "/opsx:apply", or "start coding from tasks".
40openspec-sync
Sync delta specs from a change into main specs using `/opsx:sync`, without archiving the change. Use when the user says "sync specs", "merge specs to main", "/opsx:sync", or needs to update main specs mid-change.
36openspec-schema
Create and manage custom workflow schemas using `openspec schema init/fork/validate/which`. Use when the user says "create a custom workflow", "custom schema", "fork a schema", or wants to define their own artifact types and dependencies.
35openspec-archive
Archive a completed change with `/opsx:archive`, merging delta specs into main specs and preserving the change for history. Use when the user says "archive the change", "finish up", "/opsx:archive", or "mark this change as done".
35openspec-new
Start a new OpenSpec change with `/opsx:new`, creating a change folder with metadata and scaffolding. Use when the user says "start a new change", "new feature", "/opsx:new", or "create an OpenSpec change".
29