sdd

Create SDD contracts with data models, API contracts, and documentation from feature ideas.

Updated Jul 3, 2026

Search Tags:#feature planning #SDD #spec-driven development #software development workflow #code predictability

Ready to run

npx skills add https://github.com/jsalio/My-sdd-flow --skill sdd-jsalio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd
Source: https://github.com/jsalio/My-sdd-flow/tree/main/sdd
Command: npx skills add https://github.com/jsalio/My-sdd-flow --skill sdd-jsalio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the Spec-Driven Development (SDD) workflow, ensuring that code is predictable and well-documented from the outset.

Core Features & Use Cases

Feature Idea to Contract: Converts feature ideas into formal SDD contracts, including data models, API contracts, and documentation.
Pipeline Entry Point: Acts as the entry point for the SDD workflow, setting the stage for further development steps.
Use Case: Ideal for users who want to plan a new feature before coding, ensuring all aspects are considered and documented.

Quick Start

Start the Spec-Driven Development process for a new feature by running /sdd.

Frequently Asked Questions about sdd

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

FAQPage Schema

What is spec-driven development and how does it improve code predictability?▼

Spec-driven development formalizes feature planning into structured contracts before coding. It improves code predictability by defining data models, API contracts, and documentation upfront, ensuring all implementation aspects are considered and documented from the outset.

How do I generate API contracts and data models from feature ideas?▼

You generate API contracts and data models by running an automated spec-driven development workflow. Providing structured input of your feature ideas or user stories triggers the conversion into formal SDD contracts and the required documentation.

Can I use spec-driven development for architecture and testing pipelines?▼

Yes, spec-driven development acts as the entry point for a broader software development workflow pipeline. After creating contracts, it sets the stage for subsequent automated steps including impact analysis, architecture planning, software testing, and documentation generation.

Do I need structured user stories to start the spec-driven development workflow?▼

Yes, structured input for feature ideas and user stories is required to start the spec-driven development workflow. Providing structured user stories ensures the automated generation of accurate data models, API contracts, and the required documentation.

What's the best way to document features before starting software development?▼

The best way to document features before coding is using spec-driven development. It formalizes feature ideas into structured contracts containing data models and API definitions, ensuring code predictability and well-documented software development from the outset.