spec-driven-development

Enforce SPEC-driven development for planning, implementing, testing, and reviewing code changes.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Thedougler/agent-template --skill spec-driven-development-thedougler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Thedougler/agent-template/tree/main/.github/skills/spec-driven-development
Command: npx skills add https://github.com/Thedougler/agent-template --skill spec-driven-development-thedougler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes the software development process by enforcing a SPEC-driven methodology, ensuring that all code changes are meticulously planned, implemented, tested, and reviewed against clear specifications.

Core Features & Use Cases

  • Formal Specification: Guides the creation of detailed SPEC documents from user intent.
  • Task Decomposition: Breaks down complex specifications into manageable, trackable tasks.
  • Spec-Compliant Implementation: Ensures code adheres strictly to defined requirements and acceptance criteria.
  • Automated Testing Guidance: Directs the creation of tests that validate against SPEC acceptance criteria.
  • Code Review Focus: Provides a framework for reviewing code specifically for adherence to specifications.
  • Use Case: When developing a new user authentication feature, this Skill ensures that all requirements, from password complexity to error handling, are documented in a SPEC, broken into tasks, implemented correctly, and thoroughly tested before release.

Quick Start

Use the spec-driven-development skill to create a new SPEC document for a user profile update feature.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I enforce spec-driven development methodology for planning and implementing code changes?

Spec-driven development is enforced by structuring all software development activities around formal SPEC and TASK documents, ensuring code changes are meticulously planned, implemented, tested, and reviewed against clear specifications.

What is the best way to decompose complex specifications into manageable trackable tasks?

The best way to decompose complex specifications is by using a structured SPEC methodology that breaks down formal specifications into manageable, trackable tasks, ensuring strict adherence to defined requirements and acceptance criteria.

How does automated testing guidance validate code against SPEC acceptance criteria?

Automated testing guidance validates code by directing the creation of tests specifically designed to check software implementation against the acceptance criteria defined within the formal SPEC documents.

Can I use formal SPEC documents to provide a framework for reviewing code adherence?

Yes, you can use formal SPEC documents to provide a structured framework for code review, evaluating implemented code specifically to ensure it adheres strictly to the defined requirements and specifications.

When do I need a formal specification methodology for my software development workflow?

You need a formal specification methodology when you want to standardize your software development workflow, ensuring traceability and quality from user intent through to deployed code by managing the entire lifecycle via structured documents.

Does spec-driven development require structured document formats for all development activities?

Yes, spec-driven development requires strict adherence to structured SPEC and TASK document formats for all development activities to ensure traceability and quality across the software lifecycle.