Systematic three-phase approach to feature development using Requirements, Design, and Tasks phases. Transforms vague feature ideas into well-defined, implementable solutions that reduce ambiguity, improve quality, and enable effective AI collaboration.
The 'spec-driven-development' skill provides a structured methodology for feature development in software systems. This skill addresses the problem of vague or ambiguous feature ideas by guiding the development process through three systematic phases: Requirements, Design, and Task Planning. The approach aims to reduce uncertainty, enhance collaboration among teams, and ensure that features are well-defined, implementable, and aligned with user needs. By transforming abstract concepts into clear, actionable plans, it enhances the quality and maintainability of software projects.
The skill's workflow is divided into three key phases. In the Requirements phase, user stories are captured, and acceptance criteria are defined using the EARS format to ensure completeness and feasibility. The Design phase focuses on creating a comprehensive technical plan, including system architecture, data models, and testing strategies. Finally, the Task Planning phase breaks the design into actionable tasks, organized in a sequence that allows incremental development. This structured approach ensures that projects proceed smoothly and remain aligned with initial requirements throughout the development lifecycle.
This skill is ideal for complex projects involving multiple integrations, components, or user interactions. It is most beneficial for high-stakes projects where minimizing ambiguity is crucial, such as AI-assisted development or team collaborations that require a shared understanding. However, it may be less suited for simple tasks or experimental prototypes that prioritize rapid iteration over structure and planning.
This skill is ideal for complex features that require multiple components or integrations, especially in high-stakes projects where rework costs are significant. It's also useful for team collaboration and AI-assisted development where clarity and structure are crucial.
The spec-driven-development skill is compatible with Claude Code, Cursor, VS Code, and Windsurf.
This methodology may not be suitable for simple bug fixes, experimental prototypes, time-sensitive hotfixes, or projects where minimal ambiguity is present.
In the Requirements phase, vague feature ideas are transformed into clear, testable requirements using user stories and acceptance criteria defined in the EARS format. Edge cases and constraints are also identified to ensure completeness.
Quick Setup:
.claude/skills/Repository
jasonkneen/kiro