spec-driven-development

Creates structured specifications before coding through a gated specify-plan-tasks-implement workflow.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill spec-driven-development-jacobthree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/JacobThree/zero-bloat-mcp-stack/tree/main/ai_blueprints/agent-skills/skills/spec-driven-development
Command: npx skills add https://github.com/JacobThree/zero-bloat-mcp-stack --skill spec-driven-development-jacobthree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents wasted engineering effort caused by ambiguous requirements by forcing a written, human-reviewed specification before any code is written, surfacing hidden assumptions early. ## Core Features & Use Cases - Gated Four-Phase Workflow: Enforces a Specify → Plan → Tasks → Implement pipeline where each phase requires human validation before advancing. - Six-Area Spec Template: Covers objective, commands, project structure, code style, testing strategy, and boundaries (Always/Ask First/Never rules). - Assumption Surfacing & Success Criteria: Translates vague requests like "make it faster" into concrete, testable targets such as LCP < 2.5s. - Use Case: When asked to build a new dashboard feature with unclear requirements, use this Skill to draft a spec with acceptance criteria, get human approval, break it into verifiable tasks, and only then implement. ## Quick Start Ask the AI to write a specification for your new feature before writing any code, covering objectives, commands, structure, style, testing, and boundaries.

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 a software specification before coding?▼

Write a spec covering six areas: objective, commands, project structure, code style, testing strategy, and boundaries. Surface your assumptions explicitly, get human review and approval, then proceed to planning and task breakdown before implementing.

What is spec-driven development workflow?▼

Spec-driven development is a gated workflow with four phases: Specify, Plan, Tasks, and Implement. Each phase requires human validation before advancing, ensuring the specification remains the shared source of truth between the engineer and stakeholders.

When should I not write a specification?▼

Skip the full spec for single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained. Even simple tasks benefit from a two-line spec with acceptance criteria, but lengthy documents are unnecessary.

How do I turn vague requirements into acceptance criteria?▼

Reframe vague requests into concrete, measurable conditions. For example, translate "make the dashboard faster" into targets like LCP under 2.5 seconds on 4G, initial data load under 500ms, and CLS under 0.1, then confirm these targets with the requester.

Should the specification be committed to version control?▼

Yes, the spec belongs in version control alongside the code. Treat it as a living document: update it when decisions or scope change, and reference the relevant spec sections in pull requests.