skills.rest
devsajad
devsajadCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-driven-development

Transforms feature ideas into requirements, design documents, and implementation tasks.

Updated Aug 27, 2026
Search Tags:#methodology#requirements#task planning#ai collaboration#design documentation#spec-driven development#ears format
One-click install
npx skills add https://github.com/devsajad/next.js-starter-kit --skill spec-driven-development-devsajad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/devsajad/next.js-starter-kit/tree/main/.claude/skills/spec-driven-development
Command: npx skills add https://github.com/devsajad/next.js-starter-kit --skill spec-driven-development-devsajad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague feature ideas often lead to ambiguous implementations, rework, and misaligned expectations. This Skill provides a structured three-phase methodology that converts rough ideas into clear requirements, technical designs, and actionable task lists before any code is written. ## Core Features & Use Cases - Requirements Gathering: Capture user stories and acceptance criteria using the EARS format (WHEN/IF/THEN patterns) to make requirements testable and unambiguous. - Design Documentation: Produce architecture overviews, component interfaces, data models, error handling plans, and documented technical decisions. - Task Planning: Break designs into sequenced, 2-4 hour implementation tasks with requirement traceability references. - Use Case: When adding a user registration feature, use this Skill to first define EARS-based acceptance criteria, then document the architecture and data models, and finally generate an ordered checklist of coding tasks for an AI assistant to execute. ## Quick Start Help me develop a spec for a new user account registration feature, starting with user stories and EARS-format acceptance criteria.

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 software requirements using the EARS format?▼

EARS (Easy Approach to Requirements Syntax) structures acceptance criteria as WHEN [event] THEN [system] SHALL [response], or IF [precondition] THEN [system] SHALL [response]. This makes each requirement testable and removes ambiguity from user stories.

What is spec-driven development and how does it work?▼

Spec-driven development is a three-phase methodology: Requirements (user stories with EARS acceptance criteria), Design (architecture, data models, error handling), and Tasks (sequenced implementation steps). Each phase builds on the previous one before coding begins.

When should I not use spec-driven development?▼

Skip this methodology for simple bug fixes with obvious solutions, rapid experimental prototypes, time-critical hotfixes, and well-established patterns with minimal ambiguity. The structured phases add overhead that only pays off for complex or high-stakes features.

Can I use spec-driven development with Claude Code or Cursor?▼

Yes, the methodology is designed for AI-assisted workflows in Claude Code, Cursor, VS Code, and Windsurf. Provide project context, work through phases sequentially, iterate conversationally, and validate outputs against the included checklists.

How do I break a design into implementation tasks?▼

Convert each design component into specific coding tasks of 2-4 hours each, sequence them using foundation-first, feature-slice, or risk-first strategies, and reference the requirements each task satisfies for traceability.

Related Skills

Explore More Software Engineering Skills→
lootloglootlog
7

prd

Generate Product Requirements Documents with sections for executive summary, user stories, technical specifications, risk analysis, and acceptance criteria.

Official
Advanced
atrislabsatrislabs

autopilot

Execute iterative Plan-Do-Review loops for feature development and bug fixing.

Official
Advanced
dain-agencydain-agency

migrate-verify

Cross-reference migration manifests with codebase files to verify task completion.

Official
Advanced
GitnappGitnapp

spike

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

Community
Advanced