specs-driven-dev

Guide specs-first development with intake interviews and artifact generation.

Updated Jun 26, 2026

Search Tags:#spec-driven #specification #SDD #EARS notation #spec-first #Given/When/Then

Ready to run

npx skills add https://github.com/luizparente/specs-driven-dev-skill --skill specs-driven-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specs-driven-dev
Source: https://github.com/luizparente/specs-driven-dev-skill/tree/main/specs-driven-dev-skill
Command: npx skills add https://github.com/luizparente/specs-driven-dev-skill --skill specs-driven-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires specs-driven-dev, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill guides users through the process of specs-first development, ensuring that specifications are fully defined and reviewed before any coding begins. It helps streamline the production of specifications and implementation plans, fostering a more efficient and error-free development process.

Core Features & Use Cases

Specs-Driven Development: Produces a complete, reviewed specification and implementation plan before coding.
Automated Intake: Runs an intake interview to clarify requirements and scope.
Artifact Generation: Generates multiple artifacts including specs, contracts, and implementation plans.
Multi-Agent Support: Supports parallel execution of tasks across multiple agents.

Quick Start

Use the specs-driven-dev skill to create a specification for a new feature.

Frequently Asked Questions about specs-driven-dev

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

FAQPage Schema

What is spec-driven development and how does it prevent coding errors?▼

Spec-driven development ensures comprehensive specifications and implementation plans are fully defined and reviewed before coding begins. This specs-first approach streamlines artifact generation like specs and contracts, fostering a more efficient and error-free development process by preventing scope creep.

How do I create a specification and implementation plan before coding?▼

You can create a specification by running an automated intake interview to clarify requirements and scope. This specs-first process guides you through artifact generation, producing detailed specs, contracts, and a comprehensive implementation plan ready for coding.

Does spec-driven development work with GitHub Copilot or Claude Code?▼

Yes, spec-driven development with this approach requires GitHub Copilot or Claude Code support. It integrates with these environments to guide specification creation and supports parallel task execution across multiple agents.

Can I execute implementation tasks in parallel across multiple agents?▼

Yes, the spec-driven development process supports parallel execution of tasks across multiple agents. After generating the reviewed specification and implementation plan, you can distribute tasks to multiple agents to execute the coding phase simultaneously.

What is the best way to document software requirements using EARS notation and Given/When/Then?▼

Spec-first development handles the production of detailed specs using notations like EARS and Given/When/Then. By running an automated intake interview, it clarifies scope and generates structured specification artifacts and contracts that standardize requirement documentation.

Are there limitations to automated intake interviews for specification creation?▼

The automated intake interview focuses on clarifying requirements and scope to produce specs, contracts, and implementation plans. A limitation is that it requires GitHub Copilot or Claude Code support, meaning it cannot operate as a standalone specification tool outside these environments.