skills.rest
nico0695
nico0695COMMUNITY
Explore all skills by this author →
GitHub

sdd-verify

Validates implemented changes against specs and tasks, producing an evidence-backed verify report and verdict.

Updated Apr 2, 2026
Search Tags:#code review#verification#quality gate#spec-driven development#openspec#compliance matrix#archive gate
One-click install
npx skills add https://github.com/nico0695/ai-tools --skill sdd-verify-nico0695
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/nico0695/ai-tools/tree/main/sdd/sdd-v2/skills/sdd-verify
Command: npx skills add https://github.com/nico0695/ai-tools --skill sdd-verify-nico0695

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementation work finishes, teams lack a rigorous, change-wide quality gate that reconciles actual code against the original proposal, tasks, and specs before archiving. This Skill performs final verification with mandatory evidence so changes cannot silently ship unverified. ## Core Features & Use Cases - Change-Wide Verification: Reconciles the full implemented change against proposal.md, tasks.md, spec.md, and design.md, not just the latest batch. - Config-Driven Command Plan: Derives test, build, lint, and typecheck commands from openspec/config.yaml and records results, skips, and blockers. - Compliance Matrix & Verdict: Produces verify-report.md with a compliance matrix, evidence log, severity-rated issues, and a pass, pass_with_warnings, or fail verdict with an archive gate. - Use Case: After sdd-apply completes a feature change, run final verification to confirm all acceptance criteria pass, then route the change to archive or back for correction. ## Quick Start Run final verification on the current change and write verify-report.md with the verdict and next recommended action.

Frequently Asked Questions about sdd-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an implemented change before archiving it?▼

Run the sdd-verify phase after implementation completes. It reads the change's proposal, tasks, spec, and design artifacts, executes quality commands from openspec/config.yaml, and writes verify-report.md with a compliance matrix and final verdict.

What is the difference between stage-qa and final verification?▼

stage-qa is batch-scoped, selective, and fast for early warning during implementation. sdd-verify is change-wide and evidence-heavy, serving as the final quality gate before archive. Passing stage-qa never satisfies final verification.

Which commands does the verification phase run?▼

Commands come from the sdd.quality_commands section of openspec/config.yaml, covering test, build, lint, and typecheck categories. Code-touching changes attempt test plus at least one of typecheck, build, or lint when configured; unconfigured categories are recorded as not_configured.

What verdicts can the verification report produce?▼

Three verdicts exist: pass (archive gate ready), pass_with_warnings (closeout review required), and fail (blocked). A fail verdict still returns status success when the verification itself completed and produced a trustworthy report.

When is verification blocked or partial?▼

Verification returns blocked when the objective is planner, implementation evidence is missing, or tooling failures prevent a credible attempt. It returns partial when meaningful work completed but required evidence or planned checks are still missing.

Related Skills

Explore More Software Engineering Skills→
rhyme17rhyme17

project-progress-tracker

Update PROGRESS.md with status markers, completion percentages, and dated notes.

Community
Basic
fearovexfearovex

sdd-archive

Merge delta specs into master specs and archive completed SDD changes.

Community
Advanced
MohamedAbdallah-14MohamedAbdallah-14
3

wz:reviewer

Automate adversarial review of implemented work against approved specs and plans.

Community
Advanced
ZaxbyHubZaxbyHub

qa-gate-disciplined-completion

Verify QA gate artifacts, tests, and lint before marking tasks complete.

Official
Intermediate