sdd-validate

Audits repository SDD structure and emits PASS/FAIL/WARN compliance reports.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/phm-aguiar/test_documentacao --skill sdd-validate-phm-aguiar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-validate
Source: https://github.com/phm-aguiar/test_documentacao/tree/main/.claude/skills/sdd-validate
Command: npx skills add https://github.com/phm-aguiar/test_documentacao --skill sdd-validate-phm-aguiar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Teams following Spec-Driven Development (SDD) need a fast way to verify that their repository contains the required structure — .github/memory/, specs/, and per-feature spec.md, plan.md, and tasks.md files — before opening a PR or starting new work. This Skill performs a read-only audit and reports exactly what is missing, empty, or out of convention. ## Core Features & Use Cases - Structural validation: Checks .github/memory/ (constitution.md, tech.md), specs/ subdirectories, and every feature folder for required artifacts with canonical sections. - PASS/FAIL/WARN report: Emits a structured compliance report where missing files are FAIL, empty or in-progress files are WARN, and every failure includes a suggested remediation action. - Content quality metrics: Uses freshness scoring (time-based tiers plus behavior-based signals) and coverage thresholds (green/yellow/red) to flag stale or incomplete specs. - Use Case: Before merging a feature branch, run the audit to confirm spec.md, plan.md, and tasks.md exist and are non-empty, then follow the suggested actions (e.g., run /sdd-explore-tech to populate an empty tech.md). ## Quick Start Ask the assistant to validate the SDD structure of this repository and report any missing or empty spec artifacts.

Frequently Asked Questions about sdd-validate

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

FAQPage Schema
How do I validate SDD structure in a repository?▼

Run the sdd-validate audit, which checks .github/memory/, specs/, and each feature folder for spec.md, plan.md, and tasks.md. It emits a PASS/FAIL/WARN report with a suggested action for every failure, and an optional bash script (check-sdd.sh) automates the structural checks.

What files does an SDD feature directory require?▼

Each feature under specs/features/<id>-<name>/ requires spec.md, plan.md, and tasks.md, all non-empty. spec.md needs canonical sections, plan.md needs four canonical sections, and tasks.md should contain tasks in DAG format.

Does the SDD validation modify any repository files?▼

No, the audit is strictly read-only and never creates or modifies files. It only reads the repository structure and reports findings, with remediation left to other commands such as /sdd-explore-tech.

What is the difference between FAIL and WARN in the SDD report?▼

FAIL means a required file or directory is completely absent, while WARN means it exists but is empty, still in progress, or optional. Feature directories not following the <id>-<name> naming pattern also receive a WARN.

How is documentation freshness measured for specs?▼

Freshness combines time-based tiers (fresh under 90 days, aging 90-180, stale 180-365, dead over 365) with behavior-based signals like deleted code paths or outdated dependency versions. Coverage thresholds use green/yellow/red bands to decide when action is needed.