skills.rest
theinterneti
theinternetiCOMMUNITY
Explore all skills by this author →
GitHub

sdd-workflow

Enforce Spec-Driven Development phases for specifying, planning, tasking, and implementing features.

Updated Apr 14, 2025
Search Tags:#code quality#software development#SDD#spec-driven development#feature implementation
One-click install
npx skills add https://github.com/theinterneti/TTA.dev --skill sdd-workflow-theinterneti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-workflow
Source: https://github.com/theinterneti/TTA.dev/tree/main/.claude/skills/sdd-workflow
Command: npx skills add https://github.com/theinterneti/TTA.dev --skill sdd-workflow-theinterneti

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the Spec-Driven Development (SDD) process is followed before writing implementation code, helping maintain quality and alignment with user needs.

Core Features & Use Cases

  • Specify Phase: Document functional specifications for user review.
  • Plan Phase: Outline technical plans and dependencies.
  • Tasks Phase: Break down tasks into isolated units with acceptance tests.
  • Implement Phase: Write test-driven code based on specifications.
  • Spike Exception: Allows prototyping without full SDD, but requires follow-up.

Quick Start

Initiate the SDD workflow for a new feature with /specify to start the process.

Frequently Asked Questions about sdd-workflow

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

FAQPage Schema
What is spec-driven development and how does it enforce feature implementation quality?▼

Spec-driven development is a workflow that mandates specifying, planning, tasking, and implementing phases before writing code. It enforces feature implementation quality by ensuring technical plans and tasks align directly with documented user needs.

How do I start the spec-driven development workflow for a new software feature?▼

You start the spec-driven development workflow by initiating the specify phase to document functional specifications. The workflow then progresses sequentially through planning, tasking, and implementing phases to ensure structured feature delivery.

Can I create a prototype without following the full spec-driven development process?▼

Yes, you can create a prototype without the full spec-driven development process using a spike exception. This allows prototyping to explore ideas, but it requires you to follow up with the complete SDD workflow afterward.

Does spec-driven development support test-driven code and task breakdown?▼

Yes, spec-driven development supports test-driven code by breaking down features into isolated task units with acceptance tests. Implementation proceeds by writing code that strictly validates these predefined task specifications.

When should I not use the full specification workflow for software development?▼

You should bypass the full specification workflow when you need rapid prototyping or exploratory coding. The workflow provides a spike exception for these scenarios, allowing immediate prototyping as long as formal SDD follows.

Related Skills

Explore More Software Engineering Skills→
Kafil99Kafil99

spec_writer

Generate detailed feature-level specifications in Markdown from high-level requirements.

Community
Intermediate
kkestellkkestell
1

kwork

Execute repository implementation plans with code changes, tests, and reviews.

Community
Advanced
faionfaionfaionfaion
4

faion-sdd-execution

Execute Specification-Driven Development tasks with L1-L6 quality gates and reflexion learning.

Community
Advanced
rhussrhuss
107

implement

Generate implementation plans and TDD cycles from validated specifications.

Community
Basic