kiro-skill

Turn vague feature ideas into structured requirements by triggering an interactive workflow that generates EARS-format acceptance criteria, detailed architecture designs, and actionable task lists.

Plan feature development using a four-phase workflow that progresses through requirements capture, design documentation, and test-driven task planning with explicit approval gates at each stage.

The EARS format captures feature requirements by structuring acceptance criteria into explicit conditions, ensuring ambiguous ideas are translated into testable and precise specifications.

Yes, you can generate design documents from a feature spec that detail system architecture, data models, and interfaces, aligning the technical design directly with captured requirements.

The feature development workflow operates without external dependencies and utilizes YAML-frontmatter metadata to structure specifications across requirements, design, and planning phases.

Use an interactive workflow with approval gates for software planning when transforming complex ideas into incremental, test-driven implementation plans requires strict alignment and phased review.