Guides you through building a feature in clear steps: turning a rough idea into testable requirements, drafting a technical design, and breaking it into implementation tasks. Also covers steering documents and testing strategy for AI-assisted work.
Claude Code
> /plugin marketplace add jasonkneen/kiro> /plugin install kiro-spec-driven@kiro-marketplace
Codex
$ npx skills add jasonkneen/kiro -a codex
Cursor
$ npx skills add jasonkneen/kiro -a cursor
Gemini CLI
$ npx skills add jasonkneen/kiro -a gemini-cli
GitHub Copilot
$ copilot plugin marketplace add jasonkneen/kiro$ copilot plugin install kiro-spec-driven@kiro-marketplace
OpenCode
$ npx skills add jasonkneen/kiro -a opencode
Windsurf
$ npx skills add jasonkneen/kiro -a windsurf
A comprehensive guide to systematic feature development using the three-phase spec process: Requirements → Design → Tasks.
New to spec-driven development? → Start with Methodology Overview
Ready to create your first spec? → Jump to Process Guide
Looking for examples? → Browse Examples & Case Studies
Need templates? → Get Ready-to-Use Templates
Working with AI? → Learn Prompting Strategies
📍 Need detailed navigation? → See Complete Navigation Index - Find content by role, problem, or learning style
Learn the foundational concepts and philosophy behind spec-driven development
Step-by-step walkthrough of the three-phase workflow
Insights into decision-making frameworks and thought processes
Effective communication techniques for AI collaboration
Practical guidance for implementing features from specs
Curated references and learning materials
Real-world case studies and complete spec examples
Ready-to-use templates and checklists
New to spec-driven development? Start here:
The Kiro MCP Server exposes Kiro's system prompts and instructions through the Model Context Protocol (MCP), allowing other AI assistants and tools to access Kiro's best practices.
Install and configure the MCP server:
# Using uvx (recommended)
uvx kiro-mcp-server
# Or install with pip
pip install kiro-mcp-server
Add to your MCP client configuration (e.g., ~/.kiro/settings/mcp.json):
{
"mcpServers": {
"kiro-prompts": {
"command": "uvx",
"args": ["kiro-mcp-server"],
"disabled": false
}
}
}
For more details, see the MCP Server Documentation.
Kiro is available as an installable Claude Code plugin with 7 skills following the agentskills.io specification.
# In Claude Code
/plugin marketplace add https://github.com/jasonkneen/kiro
/plugin install kiro-spec-driven@kiro-marketplace
Once installed, Claude automatically uses these skills when relevant:
| Skill | Description | Use When |
|---|---|---|
| spec-driven-development | Master methodology | "create a spec for..." |
| requirements-engineering | EARS format | "write requirements for..." |
| design-documentation | Technical architecture | "design the architecture..." |
| task-breakdown | Implementation planning | "break down into tasks..." |
| ai-prompting | AI communication | "how to prompt better..." |
| quality-assurance | Testing strategies | "testing strategy for..." |
| troubleshooting | Problem resolution | "debug this issue..." |
| create-steering-documents | Project guidelines | "create steering documents..." |
# User scope (available everywhere)
/plugin install kiro-spec-driven@kiro-marketplace
# Project scope (shared via git)
/plugin install kiro-spec-driven@kiro-marketplace --scope project
./scripts/validate-skills.sh
For more details, see the Plugin Documentation and Skills Documentation.
This guide is designed to be both a learning resource and a reference manual. Jump to any section based on your current needs, or read through sequentially for comprehensive understanding.
📍 For detailed navigation by role, problem, or learning style, see the Complete Navigation Index
Stars on GitHub
Helps you take a change from a rough idea or bug report through to a tested, reviewed result, with each step handled by a focused skill. Its skills cover pinning down domain terms, designing module interfaces, diagnosing hard bugs, and reviewing changes against your repo's coding standards.
@mattpocockA development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
@obraGives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
@affaan-mDeveloper tools for working on the React codebase itself. Provides skills for extracting error messages, managing and debugging feature flags across release channels, running Flow type checks, and fixing lint and formatting issues before committing.
@facebookGuides you through building a feature in clear steps: turning a rough idea into testable requirements, drafting a technical design, and breaking it into implementation tasks. Also covers steering documents and testing strategy for AI-assisted work. Install it with the command on its page. It includes ai-prompting, create-steering-documents, design-documentation. Its skills do not fire on their own yet. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it