sdd-spec-generator

Generates SDD specification documents with business rules, API contracts, and database schemas.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill sdd-spec-generator-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec-generator
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/sdd-spec-generator
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill sdd-spec-generator-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It converts unstructured feature requirement discussions into precise, testable SDD Spec documents before story creation, preventing scope creep and ambiguous acceptance criteria in agent-driven development workflows. ## Core Features & Use Cases - Structured Spec Generation: Produces a single {story-id}-spec.md containing Business Rules (EARS format), API contracts, SQL Server data models, and boundary conditions for M/L/XL complexity stories. - Requirement Validation: Enforces a completeness checklist (non-goals, success signals, roles, error handling) and requires asking the user instead of guessing missing details. - Architecture Alignment: Reads existing architecture documents to match MVC layering, naming conventions, error code formats, and routing patterns. - Use Case: Before running a create-story workflow for a new payment feature, generate the SDD Spec so acceptance criteria map directly to testable business rules and the dev-story TDD cycle has a clear contract. ## Quick Start Ask the AI to generate an SDD spec for your feature, for example: generate a spec for the coupon discount feature with complexity M.

Frequently Asked Questions about sdd-spec-generator

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

FAQPage Schema
How do I generate an SDD spec before creating a story?

Invoke the skill with a trigger like "generate spec" after discussing the feature requirements. It reads your architecture documents, validates requirement completeness by asking about gaps, then writes a spec file to docs/implementation-artifacts/specs/epic-{X}/.

What does an SDD specification document contain?

The spec contains a problem statement, scope boundaries, user roles, measurable success signals, EARS-format business rules, SQL Server data model DDL, API endpoint contracts with error codes, boundary conditions, security considerations, and migration notes.

When should I skip generating an SDD spec?

Skip it for S-complexity stories, where acceptance criteria with embedded business rules are sufficient. The skill is designed only for M, L, and XL complexity stories that need an independent specification as a development constraint boundary.

Does the SDD spec generator create test cases or stories?

No. Test specification tables are produced by the create-story workflow step-06, and stories themselves come from the create-story workflow. This skill only outputs the SDD Spec document with business rules, API contracts, and schema definitions.

Why must business rules use the EARS format?

EARS patterns (WHEN/IF/WHILE ... SHALL ...) make each rule independently testable with clear input-to-output expectations. This aligns the spec with the create-story template's EARS plus BDD dual-layer acceptance criteria and drives reliable TDD in dev-story.