From openspec-rewrite
This skill should be used when the user asks to "verify implementation", "validate a change", "check if implementation is complete", or "review before archiving" an OpenSpec change.
npx claudepluginhub tim-hub/powerball --plugin openspec-rewriteThis skill uses the workspace's default tool permissions.
Verify that an implementation matches the change artifacts (specs, tasks, design).
Validates implementation against change artifacts using /opsx:verify, checking completeness, correctness, and coherence. Categorizes issues as CRITICAL, WARNING, SUGGESTION before archiving.
Verifies implementation completion by running tests, code hygiene review, spec compliance validation, and drift checks; blocks claims on failures. Use before commits or merges.
Reviews code implementation against task file requirements, extracting and verifying every spec scenario (WHEN/THEN) and Done When criterion. Identifies and reports gaps before shipping.
Share bugs, ideas, or general feedback.
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
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.
Check status to understand the schema
openspec status --change "<name>" --json
Parse the JSON to understand:
schemaName: The workflow being used (e.g., "spec-driven")Get the change directory and load artifacts
openspec instructions apply --change "<name>" --json
This returns the change directory and context files. Read all available artifacts from contextFiles.
Initialize verification report structure
Create a report structure with three dimensions:
Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
Verify Completeness
Task Completion:
- [ ] (incomplete) vs - [x] (complete)Spec Coverage:
openspec/changes/<name>/specs/:
Verify Correctness
Requirement Implementation Mapping:
Scenario Coverage:
Verify Coherence
Design Adherence:
Code Pattern Consistency:
Generate Verification Report
Follow the format in references/verification-report-format.md: summary scorecard table, issues grouped by CRITICAL/WARNING/SUGGESTION, final assessment.
Verification Heuristics and Graceful Degradation
See references/verification-guidelines.md for heuristics (false positive thresholds, actionability rules) and graceful degradation rules (what to skip when artifacts are absent).