spec-driven-development

Create specifications before coding using a four-phase Specify, Plan, Tasks, Implement workflow.

Updated May 25, 2026

Search Tags:#software engineering #development workflow #specification #development process #requirements management

Ready to run

npx skills add https://github.com/huuhiep0303/s-tools --skill spec-driven-development-huuhiep0303

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/huuhiep0303/s-tools/tree/main/.agents/skills/spec-driven-development
Command: npx skills add https://github.com/huuhiep0303/s-tools --skill spec-driven-development-huuhiep0303

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of unclear or ambiguous requirements by promoting a structured approach to specification creation before coding begins.

Core Features & Use Cases

Specification Creation: Encourages writing detailed specifications before coding to clarify requirements and prevent misunderstandings.
Gated Workflow: Provides a four-phase workflow (Specify, Plan, Tasks, Implement) to ensure thorough planning and validation.
Spec Documentation: Offers a template for writing comprehensive specifications covering objectives, commands, project structure, code style, testing strategy, and boundaries.
Living Document: Emphasizes the importance of updating the specification as the project evolves.

Quick Start

Use the spec-driven-development skill to start a new project by writing a specification for your feature or change.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

How do I write clear software requirements before coding begins?▼

Spec-driven development provides a structured workflow to write detailed specifications covering objectives, project structure, and testing strategy before coding begins. This approach clarifies requirements and prevents misunderstandings by validating plans thoroughly before implementation starts.

What is the best way to manage the development workflow for a new feature?▼

Managing a development workflow effectively is best achieved using a gated, four-phase process: Specify, Plan, Tasks, and Implement. This ensures thorough planning and validation at each stage, reducing ambiguity and keeping requirements well-defined and testable throughout the project lifecycle.

How do you maintain a specification as a living document during a project?▼

Maintaining a specification as a living document requires continuously updating the requirements as the project evolves. By treating the spec as an active reference, developers ensure that objectives, code style, and testing boundaries remain accurate and aligned with the current implementation state.

Does spec-driven development work without external dependencies?▼

Spec-driven development works entirely without external dependencies, utilizing only internal scripts and reference components. It provides a self-contained workflow for creating, reviewing, and maintaining specifications, making it suitable for any software engineering environment regardless of the specific tech stack.

When should I not use a specification-driven development process?▼

You should not use a specification-driven development process when requirements are completely undefined or rapidly changing without any baseline. This approach relies on creating detailed, testable boundaries and project structure documentation upfront, which requires a minimum level of project definition to be effective.