mcpField
O
openspec-verify

openspec-verify

github.com/full-stack-skillsTesting & quality189 installsUpdated 4w ago
Repository

About openspec-verify

A skill that uses `/opsx:verify` to check whether an implementation matches its change artifacts. It evaluates completeness, correctness, and coherence, then reports findings by severity.

Key features

  1. 01Check task and requirement coverage
  2. 02Compare implementation with specification intent
  3. 03Review consistency of design and code
  4. 04Classify findings by severity

Use cases

  1. 01Validate work after implementing tasks
  2. 02Review a change before archiving
  3. 03Find issues and rerun verification after fixes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-verify

After installing, type/openspec-verifyin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

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

  1. Run verification

    • /opsx:verify — verify the current/inferred change.
    • /opsx:verify <change-name> — verify a specific change.

  2. Three verification dimensions

    DimensionWhat it validates
    CompletenessAll tasks done, all requirements implemented, scenarios covered
    CorrectnessImplementation matches spec intent, edge cases handled
    CoherenceDesign decisions reflected in code, patterns consistent

  3. Review the report

    • CRITICAL: Must fix before archiving.
    • WARNING: Should address; does not block archive.
    • SUGGESTION: Optional improvements.

  4. Fix issues if needed

    • Address critical issues, optionally fix warnings.
    • Run /opsx:verify again to confirm.

Outputs

  • Verification report with categorized issues (CRITICAL / WARNING / SUGGESTION).
  • Summary: ready to archive or not.

Next Steps

  • If ready: use openspec-archive to archive the change.
  • If issues found: fix code or update artifacts, then re-verify.

Troubleshooting

  • Many false positives: Add project context in openspec/config.yaml to help the agent understand conventions. See openspec-config.

References

Comments

Markdown supported