spec-driven-development
/spec-driven-development
Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then.
- Author
- VoDaiLocz ↗
- Repository
- kilo-kit-mcp ↗
- Licence
- Apache-2.0
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then.
Original author description
Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then.
How it works
- Why SDD in 2026?
- When to Use
- Core Workflow (The SDD Lifecycle)
- Spec Template (spec-template.md)
- Implementation Plan Structure (plan-template.md)
- Quality Gates
- Best Practices
- References & Resources
SKILL.md preview
--- name: "spec-driven-development" description: >- Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then. --- # Spec-Driven Development (SDD) SDD is the professional standard for high-assurance, agentic software engineering in 2026. It reverses the traditional "code-first" approach, elevating specifications to the primary system artifact. By ensuring code is merely a verified expression of precise specs, we eliminate ambiguity, technical debt, and misaligned requirements. ## Why SDD in 2026? As AI agents become the primary contributors to codebases, the bottleneck has shifted from *writing code* to *defining intent*. SDD provides: - **Alignment:** Ensures AI agents work on the exact problem identified by the human. - **Traceability:** Every line of code can be traced back to an acceptance criterion in a spec. - **Verification:** Specs serve as the "ground truth" for automated test suites and agent-based verification. - **Efficiency:** Reduces the need for costly refactoring by catching logic errors at the specification phase rather than the production phase. ## When to Use - **New Features:** Implementing non-trivial functionality. - **System Design:** Defining architecture, data flows, or API contracts. - **Refactoring:** When changing existing systems where behavioral preservation is critical. - **Complex Logic:** When business rules are nuanced and prone to ambiguity. - **Agent Orchestration:** When directing multiple agents, specs act as the shared project language. ## Core Workflow (The SDD Lifecycle) 1. **Idea → PRD:** Iterate with an AI agent to clarify the problem, user value, and constraints. 2. **PRD → Spec:** Translate the PRD into an executable feature specification using User Stories and Acceptance Scenarios. 3. **Spec → Implementation Plan:** Derive the technical approach. Ensure every technical decision is explicitly traced to a requirement in the spec. 4. **Plan → Code Generation:** Use the plan to generate, review, and integrate code. 5. **Feedback → Evolution:** Feed production metrics, user behavior, and edge-case discoveries back into the spec to keep the system's "truth" updated. ## Spec Template (`spec-template.md`) Use this structure to define features: ```markdown # Feature: [Name] ## Context - Business Value: [Why are we building this?] - Priority: [P1/P2/P3] ## User Stories - Given [Persona/Condition], When [Action], Then [Expected Result]. ## Acceptance Scenarios 1. Scenario: [Title] - Given: [Prerequisites] - When: [Trigger] - Then: [Outcome] ## Constraints & Edge Cases - [Constraints] - [Edge Cases] ``` ## Implementation Plan Structure (`plan-template.md`) ```markdown # Implementation Plan: [Feature Name] ## Objective - [Core goal mapped to Spec requirement #] ## Technical Strategy - [Module/Component Changes] - [Data Flow/Schema Updates] - [Dependencies] ## Verification Plan - [How do we confirm this matches the Spec?] - [Testing strategy] ``` ## Quality Gates SDD succeeds only when verified. Enforce these gates: 1. **The Independence Gate:** Every user story must be testable in isolation. 2. **The Traceability Gate:** No code change may exist without a referenced spec requirement. 3. **The Consistency Gate:** Continuous validation—every time a plan is generated, check if it contradicts existing spec constraints. ## Best Practices - **Spec-First, Code-Last:** Never touch an editor until the spec is approved. - **Research-First:** Use research agents to gather context, API documentation, and existing codebase constraints *before* drafting specs. - **Bidirectional Feedback:** Treat specs as living documents. If production deviates from the spec, update the spec first. - **Branching for Exploration:** If uncertain about technical direction, create multiple implementation plans from the same spec to evaluate trade-offs. ## References & Resources - [spec-kit framework](https://github.com/spec-kit) - [templates/](https://github.com/spec-kit/templates/) - See `skills/spec-driven-development/` for local examples. --- *SDD: If it isn't specified, it doesn't exist.*
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · VoDaiLocz/kilo-kit-mcp | 100 | Apache-2.0 |
| magnus919/agent-skills | 100 | MIT |
| lucasouzadev/agent-kit-skill | 100 | MIT |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| DanielCryer/spec-workflow | 100 | MIT |
| ctoforaday/special-circumstances | 100 | MIT |
| krzysztofsurdy/code-virtuoso | 100 | MIT |
| rafidone/agent-skills | 100 | MIT |
| sickn33/agentic-awesome-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 48113b642991 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100feature-spec
Turn an approved PRD or feature description into an engineering-ready feature spec with user stories, Given/When/Then acceptance criteria, edge cases, empty, loading and error states, analytics events, dependencies and a rollout plan. Use when a PM or designer needs to hand a… - 100sdd-spec
Create a PRD for a new feature or change (agent PRD .md; language per LANGUAGE.md + preferences under features/). Feeds sdd-plan. Use when creating a spec or invoking /sdd-spec. - 90product-spec
Write a product requirements document (PRD) or feature spec. Use when the user describes a feature or product idea and asks for a spec, PRD, requirements, user stories, "scope this", or something to hand to engineers or designers. - 100product-spec
Use when the user needs to scope, write, or audit a product spec — a PRD, feature spec, user stories, acceptance criteria, or a "spec this out"/"break this into stories"/"definition of done" request — or wants an existing spec reviewed for gaps and anti-patterns. Triggers… - 95memstack-product-feature-spec
Use this skill when the user says 'feature spec', 'spec this feature', 'write a spec', 'functional requirements', or needs a detailed specification for one feature with user flows, edge cases, API definitions, and acceptance criteria. Do NOT use for full PRDs or user story generation. - 100bdd-spec
Create or update implementation-ready Markdown feature specifications with acceptance criteria and Given/When/Then scenarios. Use for specs, PRDs, requirements documents, BDD, or Gherkin requests.