spec-driven-development

Enforce a mandatory specification phase before code implementation.

Updated Jul 31, 2026

Search Tags:#workflow #planning #development #architecture #specification #engineering

Ready to run

npx skills add https://github.com/fsolla/teqo --skill spec-driven-development-fsolla

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the ambiguity and wasted effort that occurs when coding without a clear plan, ensuring that requirements are fully understood and validated before any implementation begins.

Core Features & Use Cases

Structured Specification: Forces the creation of a shared source of truth covering objectives, tech stack, and success criteria.
Gated Workflow: Implements a four-phase process (Specify, Plan, Tasks, Implement) that requires human validation at every stage.
Use Case: When starting a complex new feature, use this skill to document assumptions and architectural boundaries, preventing costly rework and scope creep.

Quick Start

Initiate the spec-driven development process by drafting a new specification document for the upcoming feature based on the provided template.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema

How do I prevent scope creep when starting complex feature development?▼

To prevent scope creep during complex feature development, enforce a mandatory specification phase to document architectural boundaries, technical plans, and task breakdowns before implementing any code. This structured approach validates requirements upfront to eliminate ambiguity and wasted effort.

What is the best way to document assumptions for ambiguous project requirements?▼

The best way to document assumptions for ambiguous project requirements is drafting a structured specification document that defines objectives, tech stack choices, and success criteria. This creates a shared source of truth ensuring alignment before the implementation phase begins.

How do I implement a gated workflow for architectural changes?▼

Implement a gated workflow for architectural changes by applying a four-phase process: Specify, Plan, Tasks, and Implement. This requires human validation at every stage, ensuring that technical plans and task breakdowns are approved before proceeding to the actual code implementation.

When do I need a structured specification before code implementation?▼

You need a structured specification before code implementation when tackling complex feature development, architectural changes, or ambiguous project requirements. Drafting objectives and technical plans first ensures alignment between human and agent, preventing costly rework later.

Does spec-driven development work for simple bug fixes and minor updates?▼

Spec-driven development is not intended for simple bug fixes or minor updates. It is designed for complex feature development and architectural changes where a mandatory specification phase is required to validate ambiguous requirements and prevent scope creep.