Generate requirements, design, and task artifacts under .kiro/specs.
npx skills add https://github.com/devkeni/Skills --skill kiro-skill-devkeni
Please help me install this Agent Skill. Skill: kiro-skill Source: https://github.com/devkeni/Skills/tree/main/ai-apps/kiro-skill Command: npx skills add https://github.com/devkeni/Skills --skill kiro-skill-devkeni
Interactive feature development workflow from idea to implementation. Creates requirements (EARS format), design documents, and implementation task lists. Use when creating feature specs, requirements documents, design documents, or implementation plans. Triggered by "kiro" or references to .kiro/specs/ directory.
Provide a feature idea and ask KIRO to guide you through requirements, design, and task planning.
High-intent search queries and answers about installing and using this skill.
Feature specs are created through a phase-gated workflow that generates structured artifacts like requirements.md, design.md, and tasks.md under the .kiro/specs directory to guide development from idea to executable task planning.
The EARS format is a structured method used to write software requirements within the requirements.md artifact, ensuring clear, testable conditions that support incremental development before design and task phases begin.
You manage pre-implementation planning through a phase-based workflow with explicit approval gates, generating and reviewing .kiro/specs artifacts sequentially to ensure alignment between requirements, design documents, and implementation task lists.
Yes, the feature specification workflow supports explicit approval gates and iterative review at each phase, ensuring team alignment and structured progression before moving from requirements to design and final task execution.
Yes, the workflow generates structured artifacts and guidance specifically to support test-driven, incremental development, breaking down design documents into organized implementation task lists for phased execution.
The .kiro/specs directory automatically organizes generated feature artifacts like requirements.md, design.md, and tasks.md into structured folders, maintaining clear documentation and traceability throughout the development lifecycle.
shimaMatzInitialize KiRo spec files from a project description and templates.
kirkchenAutomate code implementation from gherkin or proposal artifacts with TDD workflows.
taku-oGenerate EARS-format requirements drafts from project specs and steering files.
Vivekmano27Generate complete project specification documents from a concise project brief.
