spec-driven-development

Draft a complete spec before coding using a four-phase workflow.

Updated Mar 11, 2026

Search Tags:#workflow #planning #architecture #documentation #requirements #spec #spec-template

Ready to run

npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill spec-driven-development-avila-tek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/Avila-Tek/avila-tek-skill-pack/tree/main/skills/dev-spec-driven-development
Command: npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill spec-driven-development-avila-tek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a complete spec before coding to align stakeholders and reduce rework.

Core Features & Use Cases

Spec-guided planning accelerates delivery by documenting objectives, constraints, and acceptance criteria before any code is written.
Works for starting new projects, features, or significant changes when requirements are unclear or evolving, ensuring all stakeholders share a single source of truth.
The resulting spec serves as the living contract for planning, implementation, and validation.

Quick Start

Create a new spec by filling out the standard template and review it with the team before implementation.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

What is spec-driven development and when should I use it?▼

Spec-driven development is the practice of drafting a complete specification before coding to align stakeholders and reduce rework. Use it when starting new projects or features with unclear, ambiguous, or evolving requirements to establish a single source of truth.

How do I write a comprehensive spec template for a new software feature?▼

To write a comprehensive spec template, document the Objective, Tech Stack, Commands, Project Structure, Code Style, Testing Strategy, and Boundaries. This structured specification serves as a living contract for planning, implementation, and validation.

How does the four-phase spec workflow work for planning and implementation?▼

The four-phase spec workflow works by sequentially moving through Specify, Plan, Tasks, and Implement phases. This process ensures that all architectural decisions are documented and verifiable before coding begins, reducing ambiguity and rework.

Does spec-driven planning work for agile workflows with evolving requirements?▼

Spec-driven planning works for agile workflows by treating the specification as a living contract. It accelerates delivery by documenting evolving objectives, constraints, and acceptance criteria, ensuring stakeholders share a single source of truth throughout changes.

Can I use spec templates for existing projects undergoing significant changes?▼

Yes, you can use spec templates for existing projects undergoing significant changes. Drafting a specification helps align stakeholders on new constraints and acceptance criteria, ensuring the modifications are documented and verifiable before implementation.

What are the limitations of spec-driven development for small projects?▼

The main limitation of spec-driven development is the overhead of drafting comprehensive documentation for Objective, Tech Stack, and Boundaries. For small projects with immediately clear requirements, this extensive planning phase may introduce unnecessary friction and delay coding.