sdd-verify

Verify code implementations against spec requirements, tasks, and design decisions before archiving changes.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill sdd-verify-alessioscarfone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-verify
Source: https://github.com/AlessioScarfone/aine-copilot-plugins/tree/main/src/sdd-team/skills/sdd-verify
Command: npx skills add https://github.com/AlessioScarfone/aine-copilot-plugins --skill sdd-verify-alessioscarfone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After implementing a change in a spec-driven development workflow, it is hard to confirm that every requirement, task, and design decision was actually addressed before merging or archiving. This Skill automates that QA review by comparing code changes against the change artifacts. ## Core Features & Use Cases - Completeness Checks: Parses tasks.md checkboxes and delta spec requirements to flag incomplete tasks and unimplemented requirements as CRITICAL issues. - Correctness & Coherence Review: Maps requirements to implementation evidence in the codebase, checks scenario and test coverage, and verifies adherence to design.md decisions. - Structured Verification Report: Produces a markdown scorecard with CRITICAL, WARNING, and SUGGESTION severities, actionable recommendations, and file:line references, then updates the change tracker to verified on a clean pass. - Use Case: After finishing an 'add-auth' feature, run the verification to confirm all spec requirements are implemented, all tasks are checked off, and the design decisions were followed before archiving the change. ## Quick Start Ask the assistant to run /sdd-verify on your implemented change, for example by saying "verify my add-auth change against its spec and tasks before I archive it".

Frequently Asked Questions about sdd-verify

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

FAQPage Schema
How do I verify my implementation against a spec before merging?▼

Run /sdd-verify with the change name, such as /sdd-verify add-auth. It loads the proposal, design, tasks, and delta specs, then checks task completion, requirement coverage, and design adherence, producing a report with CRITICAL, WARNING, and SUGGESTION issues.

What does the sdd-verify verification report contain?▼

The report includes a summary scorecard covering completeness, correctness, and coherence, followed by issues grouped by severity. Each issue has an actionable recommendation with file:line references, plus a final assessment stating whether the change is ready for archive.

Can I run verification without specifying a change name?▼

Yes. If no change name is given, the skill lists available changes in the change folder that have a tasks.md file and prompts you to select one. Changes with incomplete tasks are marked as In Progress, and it never auto-selects a change.

What happens if my change has no design.md or specs?▼

The skill degrades gracefully and verifies only what exists. It can check tasks alone, tasks plus specs, or all three dimensions, and it always notes which checks were skipped in the report.

When should I not use sdd-verify?▼

Do not use it for implementing changes, creating artifacts, or archiving a change without prior verification. It is strictly a QA review step that runs after implementation and before archiving.