
Spec Driven Development
This is a structured three-phase methodology for breaking down features into Requirements (using EARS format for acceptance criteria), Design (architecture and technical decisions), and Tasks (sequenced implementation steps). It shines when you're building complex features where rework is expensive or when working with AI assistants that need clear structure to generate quality code. The checklists and traceability between phases help catch gaps early. Skip it for simple bug fixes or quick prototypes, but for anything involving multiple components or team collaboration, the upfront investment pays off in reduced ambiguity and fewer surprises during implementation. Essentially turns "build a user authentication system" into a spec you can actually execute against.
- skills.sh installs
- 452
- GitHub stars
- 757
- last updated
- Aug 21, 2026
Install
$ npx -y skills add jasonkneen/kiro --skill spec-driven-development --agent claude-codeInstalls into .claude/skills of the current project.
Files
Spec-Driven Development
A comprehensive methodology for systematic software feature development that ensures quality, maintainability, and successful delivery through structured planning.
When to Use This Skill
Ideal scenarios:
- Complex features with multiple components, integrations, or user interactions
- High-stakes projects where rework costs are significant
- Team collaboration requiring shared understanding
- AI-assisted development where clear structure improves output quality
- Knowledge preservation for future maintainers
Less suitable:
- Simple bug fixes with obvious solutions
- Experimental prototypes for rapid iteration
- Time-critical hotfixes requiring immediate action
- Well-established patterns with minimal ambiguity
The Three-Phase Workflow
Phase 1: Requirements Gathering
Purpose: Transform vague feature ideas into clear, testable requirements
Process:
- Capture user stories expressing value and purpose
- Define acceptance criteria using EARS format (Easy Approach to Requirements Syntax)
- Identify edge cases and constraints
- Validate completeness and feasibility
Sponsors
Details
- Repository
- github.com/jasonkneen/kiro
- Categories
- Code Review & Quality, Design & UI/UX
- First seen
- Jun 3, 2026