kiro-skill
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.
Security Assessment
About kiro-skill
The kiro-skill is an interactive workflow tool designed to transform ideas into fully structured feature specifications, design documents, and actionable implementation plans. It addresses the common challenge of moving from a high-level concept to a clear, executable development plan by providing a guided, phase-driven process. By standardizing requirements gathering, design, and task creation, it reduces ambiguity and ensures that features are well-defined, technically feasible, and aligned with user needs.
The skill's main capabilities include generating requirements in the EARS format with user stories and acceptance criteria, creating design documents that outline architecture, components, and data models, and producing implementation task lists that support incremental, test-driven development. It facilitates a structured approach where files are automatically stored in a dedicated `.kiro/specs/{feature-name}/` directory using kebab-case naming. The workflow emphasizes minimal and precise code, follows existing patterns, and encourages iterative review and approval at each stage to ensure clarity and alignment before proceeding to the next phase.
Kiro-skill is particularly useful for software developers, product managers, and technical leads who are planning new features or systems. It is suitable for teams looking to standardize documentation, streamline development planning, and maintain a clear trace from requirements to implementation. Ideal use cases include drafting feature specifications, defining acceptance criteria, designing system architecture, planning implementation tasks, and executing tasks directly from a spec. Its interactive and human-like guidance makes it accessible for developers seeking support without prescriptive instructions.
FAQ
How do I start using kiro-skill for a new feature?
You trigger the skill by mentioning a feature spec, design document, or implementation plan, or by referencing the .kiro/specs/ directory. It will guide you through generating requirements, design, and tasks.
What format does kiro-skill use for requirements?
Requirements are written in EARS format with user stories and structured acceptance criteria, including event-driven, conditional, state-driven, ubiquitous, and unconditional statements.
Where are the generated files stored?
All files are stored in the `.kiro/specs/{feature-name}/` directory, with feature names in kebab-case (e.g., 'user-authentication').
Can kiro-skill execute implementation tasks automatically?
It provides a plan and task list for execution, supporting a test-driven, incremental approach, but it does not directly run or deploy code.
Who is the target user for this skill?
Software developers, product managers, and technical leads who need structured workflows for feature specification, design, and implementation planning.
Install kiro-skill
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
Microck/ordinary-claude-skills