菜单
Validate that implementation matches specs, design, and tasks. Trigger: When the user wants to verify a completed or partially completed change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | openspec-verify |
| description | Validate that implementation matches specs, design, and tasks. Trigger: When the user wants to verify a completed or partially completed change. |
| license | MIT |
| compatibility | Requires openspec CLI. |
| metadata | {"author":"gentleman-programming","version":"2.0"} |
Validate that the implementation matches what was planned. Check completeness (all tasks done?), correctness (code matches specs?), and coherence (design decisions followed?).
Select the change
If not provided, run:
openspec list --json
And ask the user to select.
Read context
openspec status --change "<name>" --json
Then read:
openspec/changes/<name>/specs/ — acceptance criteriaopenspec/changes/<name>/tasks.md — what was plannedopenspec/changes/<name>/design.md — how it should be builtRun tests if available
Check if the project has a test runner and run it:
# Examples:
npm test
go test ./...
pytest
Check completeness
Count - [x] vs - [ ] in tasks.md.
Report: "N/M tasks complete"
Check correctness
For each spec requirement:
Check coherence
For key design decisions:
Build the compliance matrix
| Requirement | Status | Notes |
|-------------|--------|-------|
| REQ-001 | PASS | - |
| REQ-002 | FAIL | Missing error handling |
Output report
Save to openspec/changes/<name>/verify-report.md.
## Verification Report: <change-name>
**Date**: YYYY-MM-DD
**Tasks**: N/M complete
### Test Results
<test output or "No test runner detected">
### Spec Compliance
| Requirement | Status | Notes |
|-------------|--------|-------|
| REQ-001 | PASS | - |
| REQ-002 | FAIL | Missing validation |
### Design Coherence
- <decision>: FOLLOWED / DEVIATED (reason)
### Summary
- CRITICAL: <blockers that must be fixed before archive>
- WARNING: <issues worth noting but not blocking>
- SUGGESTION: <improvements for the future>
**Verdict**: READY FOR ARCHIVE / NEEDS FIXES
rules.verify from openspec/config.yamlImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Create a technical design document for a change using the openspec CLI. Trigger: When the orchestrator or user needs a design document created or updated for a change.
Initialize OPSX in a project. Runs `openspec init` to scaffold the openspec/ directory and config. Trigger: When user wants to initialize OPSX in a project, or says "opsx init", "iniciar opsx", "openspec init".
Guided end-to-end walkthrough of the OPSX workflow using the real codebase. Trigger: When the user wants to learn OPSX or do a guided first change.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Write or update specifications for a change using the openspec CLI. Trigger: When the orchestrator or user needs specs created or updated for a change.