Build Feature from Spec to Task

Transform feature ideas into specifications (EARS format), design documents, and incremental implementation task lists

Feature development where spec-first methodology improves clarity and reduces implementation rework.

• · Rough feature idea or problem statement
• · User feedback and iteration on requirements/design
• · Implementation constraints (tech stack, timeline)

• · requirements.md with user stories and EARS acceptance criteria
• · design.md with architecture, data models, and component breakdown
• · tasks.md with test-driven, incremental implementation steps
• · .kiro/specs/{feature-name}/ directory with all documents

• · Markdown editor (any $EDITOR)
• · File system (Read, Write, Edit tools)
• · Bash for mkdir/touch (fs operations)
• · WebSearch / WebFetch (optional, for research during requirements)

• · User able to describe the feature in conversational terms
• · No prior spec documents needed — Kiro generates from scratch
• · Feature complexity within single-feature scope (not multi-phase epics)

• · Initial spec overly ambitious (too many requirements) → slows design phase
• · User feedback loop stalls (unclear on what to change in next revision)
• · Requirements ambiguous on acceptance criteria → design phase faces gaps
• · Task estimation in design phase may miss dependencies (sequential work becomes blocked)

• · EARS acceptance criteria format (event-driven, conditional, state, ubiquitous)
• · Iterative three-phase workflow (Requirements → Design → Tasks)
• · Human-friendly tone (not verbose, avoids fluff)
• · Kebab-case naming convention for file organization