skills.rest
CodeCrafterAdi2006
CodeCrafterAdi2006COMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-driven-development

Writes structured specifications before coding through a gated four-phase workflow.

Updated Jul 10, 2026
Search Tags:#workflow#planning#documentation#specification#requirements#task breakdown#acceptance criteria
One-click install
npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill spec-driven-development-codecrafteradi2006
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/CodeCrafterAdi2006/Ink-and-Code/tree/main/Skills/spec-driven-development
Command: npx skills add https://github.com/CodeCrafterAdi2006/Ink-and-Code --skill spec-driven-development-codecrafteradi2006

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: Progresses through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Six-Section Spec Template: Covers objective, commands, project structure, code style, testing strategy, and Always/Ask First/Never boundaries. - Assumption Surfacing: Lists assumptions explicitly and reframes vague requirements into testable success criteria. - Use Case: When asked to build a new feature with only a vague description, use this Skill to draft a spec with concrete acceptance criteria, get it approved, then break it into dependency-ordered tasks saved to tasks/plan.md and tasks/todo.md. ## Quick Start Ask the agent 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 specification before coding a new feature?▼

Start by listing your assumptions explicitly, then write a spec covering six areas: objective, commands, project structure, code style, testing strategy, and boundaries. Have a human review and approve it before moving to planning and implementation.

What is spec-driven development workflow?▼

It is a gated four-phase workflow: Specify, Plan, Tasks, Implement. Each phase requires human review before advancing, ensuring the specification remains the shared source of truth between the engineer and stakeholders.

When should I skip writing a spec?▼

Skip the full spec only 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.

How do I turn vague requirements into testable criteria?▼

Reframe each vague requirement as concrete success criteria with measurable targets. For example, translate "make the dashboard faster" into LCP under 2.5 seconds, data load under 500ms, and CLS under 0.1, then confirm the targets with stakeholders.

What are the limitations of spec-driven development?▼

It adds upfront time before coding begins, which can feel slow for trivial changes. It also requires discipline to keep the spec updated as decisions and scope change, since an outdated spec loses value.

Related Skills

Explore More Software Engineering Skills→
d3mingd3ming

write-a-prd

Draft product requirements documents from user interviews and repository inspection.

Community
Advanced
WizarckWizarck
2

bmad-agent-dev

Executes approved development stories with test-driven implementation and acceptance criteria tracking.

Community
Intermediate
speqqaispeqqai

writing-plans

Generate a step-by-step implementation plan from a project spec.

Official
Advanced
GitnappGitnapp

spike

Validate uncertain technical ideas through focused throwaway experiments before production implementation.

Community
Advanced