Agent Skills: OpenSpec Verify Change

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

UncategorizedID: u473t8/learning-app/openspec-verify-change

Install this agent skill to your local

pnpm dlx add-skill https://github.com/u473t8/learning-app/tree/HEAD/.codex/skills/openspec-verify-change

Skill Files

Browse the full folder contents for openspec-verify-change.

Download Skill

Loading file tree…

.codex/skills/openspec-verify-change/SKILL.md

Skill Metadata

Name
openspec-verify-change
Description
Verify that implementation matches an OpenSpec change before archiving. Use this when the user wants a completion check across tasks, specs, design, and code before calling the change done.

OpenSpec Verify Change

Use this skill for a verification pass before archive.

Workflow

  1. Resolve the target change.

  2. Run OpenSpec validation first:

openspec validate "<name>" --type change --json
  1. Inspect workflow state:
openspec status --change "<name>" --json
openspec instructions apply --change "<name>" --json
  1. Read all available contextFiles.

  2. Verify three dimensions:

    • completeness: incomplete tasks, missing artifacts, obviously unimplemented requirements
    • correctness: implementation or tests that appear to diverge from the change
    • coherence: design mismatches or project-pattern regressions
  3. Report findings first, ordered by severity.

Output

Use a review-style result:

  • CRITICAL: must fix before archive
  • WARNING: likely gaps or divergences
  • SUGGESTION: smaller improvements

If there are no findings, say so explicitly and mention any residual uncertainty.

Guardrails

  • Prefer concrete file references.
  • Treat OpenSpec validation output as a baseline, not the whole answer.
  • When uncertain, downgrade severity instead of overstating.