spec-driven-dev

Creates specifications, plans, and guides test-first implementation for software development projects requiring git and defined file structures.

11|Updated Jun 19, 2013
One-click install
npx skills add https://github.com/MadBomber/experiments --skill spec-driven-dev-madbomber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/MadBomber/experiments/tree/main/ai_misc/skills/rocka-spec-driven-dev
Command: npx skills add https://github.com/MadBomber/experiments --skill spec-driven-dev-madbomber

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the common issue of jumping straight into coding without a clear plan, leading to design flaws, rework, and wasted effort. It enforces a structured development process to ensure features are well-defined, planned, reviewed, and implemented efficiently.

Core Features & Use Cases

  • Structured Workflow: Guides users through Specify → Plan → Review → Build phases.
  • Specification: Helps create detailed feature specifications.
  • Planning: Facilitates breaking down features into testable stories with acceptance criteria and test contracts.
  • Review: Incorporates a "devil's advocate" review step to catch potential issues early.
  • Test-First Development: Emphasizes writing tests before implementation to ensure quality and define "done."
  • Use Case: When starting a new, complex feature, use this Skill to ensure all requirements are captured, the implementation is well-thought-out, and the development process is robust and testable.

Quick Start

Use the spec-driven-dev skill to start building a new feature by first creating a specification document.

Frequently Asked Questions about spec-driven-dev

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

FAQPage Schema
What is a structured software development workflow and why use it?

A structured software development workflow moves from specification through planning and review to test-driven implementation, preventing design flaws and wasted effort caused by jumping straight into coding without a clear plan.

How do I plan complex features into testable stories with acceptance criteria?

You can plan complex features by creating detailed specifications, then breaking the work down into testable stories complete with acceptance criteria and test contracts to guide test-first development.

Does test-driven development require git version control?

Yes, the test-driven development workflow requires git for version control and strict adherence to a defined file structure for managing your specifications, plans, and tests.

How does a devil's advocate review improve feature planning?

A devil's advocate review improves feature planning by critically evaluating the broken-down stories and specifications during the review phase, which helps catch potential design issues early before implementation begins.

Can I use this specification-driven approach for existing agile projects?

Yes, you can integrate this specification-driven approach into agile projects by applying the Specify, Plan, Review, and Build phases to new complex features to ensure requirements are captured and thoroughly tested.