kiro-skill

Orchestrate feature development workflows from idea to implementation.

2|Updated Mar 25, 2026

Search Tags:#workflow #design #planning #collaboration #requirements #feature-development

Ready to run

npx skills add https://github.com/billlzzz26/note-taker-convex-ai-convex --skill kiro-skill-billlzzz26

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kiro-skill
Source: https://github.com/billlzzz26/note-taker-convex-ai-convex/tree/main/.agents/skills/kiro-skill
Command: npx skills add https://github.com/billlzzz26/note-taker-convex-ai-convex --skill kiro-skill-billlzzz26

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns vague feature ideas into a structured, executable workflow, automating the creation of requirements, designs, and task planning to accelerate delivery and alignment.

Core Features & Use Cases

Generates requirements in EARS format from user ideas to capture acceptance criteria.
Produces design documents detailing architecture, data models, and interfaces.
Creates actionable task lists aligned to the design for incremental, test-driven implementation.
Triggers: "kiro", ".kiro/specs/", "feature spec", "需求文档", "设计文档", "实现计划".

Quick Start

Mention a feature idea to trigger the kiro workflow and begin creating initial specs.

Frequently Asked Questions about kiro-skill

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

FAQPage Schema

How do I turn vague feature ideas into structured requirements and design documents?▼

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.

What is the best way to plan feature development from initial idea to implementation tasks?▼

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.

How does the EARS format help capture feature requirements accurately?▼

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

Can I generate design documents detailing architecture and data models from a feature spec?▼

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.

Does this feature development workflow require any external dependencies or specific file formats?▼

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

When should I use an interactive workflow with approval gates for software planning?▼

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.