kiro-skill

Orchestrate multi-phase feature development from requirements to executable code.

22|6|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/Aniket-a14/SRA --skill kiro-skill-aniket-a14
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-skill
Source: https://github.com/Aniket-a14/SRA/tree/main/.gemini/skills/kiro-skill
Command: npx skills add https://github.com/Aniket-a14/SRA --skill kiro-skill-aniket-a14

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the entire feature development process, transforming a raw idea into executable code through structured requirements, design, and task planning.

Core Features & Use Cases

  • Requirements Gathering: Defines feature specifications in EARS format with user stories and acceptance criteria.
  • Design Document Creation: Generates architecture, component, and data model designs based on requirements.
  • Implementation Task Planning: Breaks down the design into test-driven, actionable tasks.
  • Task Execution: Guides the implementation of individual tasks one by one.
  • Use Case: You have a new idea for a user profile editing feature. Kiro will help you write the requirements, design the backend and frontend components, create a list of coding tasks, and then help you implement those tasks step-by-step.

Quick Start

Use the kiro skill to start creating a new feature specification for a user login system.

Frequently Asked Questions about kiro-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure feature requirements before implementation?

Feature requirements are structured using the EARS format, which defines specifications alongside user stories and acceptance criteria to ensure clear implementation goals before coding begins.

What is the best way to plan feature development from idea to code?

The best way to plan feature development is through an interactive workflow that progresses from requirements definition to technical design documentation, ending with test-driven task breakdown for iterative implementation.

How do I break down technical design into actionable coding tasks?

Technical design is broken down into actionable coding tasks through a structured task planning phase that generates test-driven, step-by-step implementation instructions based on the architecture and component designs.

Does this feature development workflow require external dependencies?

No, this feature development workflow operates independently without external dependencies, relying solely on its internal scripts and references to guide the specification and implementation lifecycle.

Can I generate architecture and data model designs from user stories?

Yes, you can generate architecture, component, and data model designs directly from gathered requirements, translating user stories and acceptance criteria into structured technical design documentation.

What is the EARS format for software requirements?

The EARS format is a structured method for defining feature requirements, utilizing specific conditions to write clear, unambiguous specifications that guide subsequent technical design and implementation phases.