ss-sdd-reviewing-specs

Review SDD-produced spec.md files against project context for planning-blocking issues.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-reviewing-specs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ss-sdd-reviewing-specs
Source: https://github.com/Emrebener/Sublime-Skills/tree/main/skills/spec-driven-development/ss-sdd-reviewing-specs
Command: npx skills add https://github.com/Emrebener/Sublime-Skills --skill ss-sdd-reviewing-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents flawed implementation plans by catching omissions, contradictions, ambiguity, and constitution/ADR misalignment in spec.md documents before they are locked for planning.

Core Features & Use Cases

  • Structured, read-only spec review: Reviews a coordinator-provided spec.md plus listed context files and returns a findings report without modifying anything.
  • Detection gates for real implementation risk: Checks completeness, internal consistency, clarity/testability, constitution and ADR alignment, scope/YAGNI, and vocabulary/glossary drift.
  • Leaf, subagent-style output for coordinators: Produces categorized findings with severity (CRITICAL/HIGH/MEDIUM/LOW) and a calibration rule of “approve unless CRITICAL/HIGH exist.”

Quick Start

Dispatch this skill as a subagent to review the SDD-generated spec.md at the provided SPEC_PATH and return the structured findings report.

Frequently Asked Questions about ss-sdd-reviewing-specs

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

FAQPage Schema
How do I validate a spec.md file for planning-breaking risks before implementation?

Spec review validates spec.md files by running a read-only detection pass against project context to identify completeness gaps, internal contradictions, untestable requirements, and ADR misalignment. It outputs a categorized findings report with severity levels to gate planning approval.

What is a read-only spec review and why is it needed for SDD workflows?

Read-only spec review is a pre-plan validation process that audits SDD-produced spec.md documents without modifying them. It is needed to catch omissions, ambiguity, and scope/YAGNI problems early, preventing flawed implementation plans from being locked in.

How do I check if my requirements specification aligns with ADRs and project constitution?

ADR alignment checking reviews a coordinator-provided spec.md against supplied project context files to detect constitution or architecture decision record misalignment. It applies quality gates and returns findings categorized by CRITICAL, HIGH, MEDIUM, or LOW severity.

Can I use automated quality gates to approve or reject a requirements specification?

Yes, quality gates evaluate spec.md files using a calibration rule that approves specifications unless CRITICAL or HIGH severity findings exist. The review process checks clarity, testability, and vocabulary drift to determine if the spec is ready for planning.

What are common scope and YAGNI problems found during requirements validation?

Requirements validation detects scope creep and YAGNI (You Aren't Gonna Need It) problems by checking for unnecessary features and untestable requirements in spec.md files. It flags these issues in a structured report to prevent over-engineering before planning begins.

How do I review an SDD-generated spec.md as a subagent without modifying files?

Dispatch a read-only spec review subagent with the provided SPEC_PATH to audit the SDD-generated spec.md. The subagent executes a detection-pass checklist against context files and returns a structured findings report without writing any changes.