sdd-specify

Name: sdd-specify
Availability: InStock
Author: umatoma

Generate Specification-Driven Development Part 1 documents through guided requirement elicitation and clarification questions.

Updated Jan 24, 2026

Search Tags:#template #documentation #software development #specification #requirements #sdd

Ready to run

npx skills add https://github.com/umatoma/claude-example --skill sdd-specify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-specify
Source: https://github.com/umatoma/claude-example/tree/main/.claude/skills/sdd-specify
Command: npx skills add https://github.com/umatoma/claude-example --skill sdd-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the initial phase of Specification-Driven Development (SDD) by guiding users through requirement clarification and generating a structured specification document (Part 1).

Core Features & Use Cases

Requirement Clarification: Asks targeted questions to resolve ambiguities and gather detailed requirements.
Specification Document Generation: Creates a comprehensive Part 1 specification document using a predefined template, covering overview, detailed specs, acceptance criteria, and more.
Project Constitution Alignment: Validates the generated specification against project principles and checklists.
Use Case: When a product manager needs to define a new feature, they can invoke this Skill, answer the clarifying questions, and receive a ready-to-review specification document that adheres to project standards.

Quick Start

Use the sdd-specify skill to create a specification for a new user login feature.

Frequently Asked Questions about sdd-specify

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

FAQPage Schema

How do I generate a specification document from raw software requirements?▼

To generate a specification document from software requirements, this Skill uses a guided Q&A process to elicit feature details, API contracts, and acceptance criteria, producing a structured SDD Part 1 document ready for review.

What is Specification-Driven Development and when do I need a Part 1 document?▼

Specification-Driven Development (SDD) is a methodology where development follows formal specifications; you need a Part 1 document to define overview, detailed specs, and acceptance criteria before proceeding to the planning phase.

How do I clarify ambiguous feature requirements before writing a specification?▼

To clarify ambiguous feature requirements before writing a specification, the Skill asks targeted questions to resolve ambiguities, iteratively refining details and flagging unclarified points for resolution.

Can I align new feature specifications with existing project constitution principles?▼

Yes, you can align new feature specifications with existing project principles; the Skill validates the generated specification against project constitution principles and checklists to ensure compliance.

What's the best way to define API contracts and data models for a new feature?▼

The best way to define API contracts and data models for a new feature is using a guided elicitation process that captures these technical details within a structured specification document aligned with development standards.

What happens if some requirements are left unclarified during specification generation?▼

If requirements are left unclarified during specification generation, the Skill identifies and flags those unclarified points, requiring resolution before you can proceed to the planning phase.