Skip to content
/

kiro (jasonkneen)

kiro-jasonkneen · jasonkneen/kiro · ★ 665 · last commit 2026-01-12

Primitive shape 11 total
Commands 2 Skills 8 MCP tools 1
00

Summary

kiro (jasonkneen) — Summary

kiro (jasonkneen) is a methodology documentation and Claude Code plugin that packages the complete Kiro IDE spec-driven development methodology as a portable skill pack for Claude Code (and Cursor, VSCode, Windsurf). It ships a .claude-plugin/ package (plugin name: kiro-spec-driven), 8 Claude Code skills covering spec-driven development phases (requirements-engineering, design-documentation, task-breakdown, ai-prompting, quality-assurance, troubleshooting, create-steering-documents), a Kiro IDE system prompt (complete-instructions.md), and a comprehensive process-guide documentation tree (spec-process-guide/). The core value is making the proprietary Kiro IDE workflow available in open AI clients, plus a standalone reference guide on spec-driven development with EARS notation. Version 1.0.0, 665 stars, MIT license, 3 contributors, last commit January 2026.

Differs from seeds: This is a direct port of the kiro seed's methodology into Claude Code's plugin format. The .kiro/system/complete-instructions.md is the verbatim Kiro IDE system prompt extracted from the IDE (identifiable by Kiro's brand voice guidelines and fsWrite tool references). Compared to cc-sdd (which is also Kiro-inspired), kiro-jasonkneen ships the actual Kiro system prompt rather than reimplementing the workflow; it has 0 CLI binary, 0 commands, 2 hooks (unknown), and relies on skills rather than explicit slash commands.

01

Overview

kiro (jasonkneen) — Overview

Origin

Created by Jason Kneen (@jasonkneen) to make the Kiro IDE methodology portable. The .kiro/system/complete-instructions.md is the verbatim Kiro IDE system prompt, identifiable by its "Identity: You are Kiro" opening, brand voice guidelines ("We are knowledgeable. We are not instructive."), and fsWrite tool references. The repository also ships example steering documents (.kiro/steering/), a comprehensive spec-process-guide documentation tree, and a Claude Code plugin manifest. 665 stars, MIT license, 3 contributors. Last commit January 2026.

Philosophy (From README)

"A comprehensive guide to systematic feature development using the three-phase spec process: Requirements → Design → Tasks."

From the Kiro system prompt (complete-instructions.md, verbatim):

"We are knowledgeable. We are not instructive. In order to inspire confidence in the programmers we partner with, we've got to bring our expertise and show we know our Java from our JavaScript. But we show up on their level and speak their language, though never in a way that's condescending or off-putting."

"We are supportive, not authoritative. Coding is hard work, we get it. That's why our tone is also grounded in compassion and understanding so every programmer feels welcome and comfortable using Kiro."

"Keep the cadence quick and easy. Avoid long, elaborate sentences and punctuation that breaks up copy (em dashes) or is too exaggerated (exclamation points)."

Key Components

  1. Verbatim Kiro system prompt (.kiro/system/complete-instructions.md) — the complete identity, capabilities, rules, and response-style guidelines from the Kiro IDE, adapted for Claude Code.
  2. 8 skills for spec-driven development phases — requirements-engineering (EARS), design-documentation, task-breakdown, etc.
  3. 2 slash commandscreate-steering-documents and create-steering-documents-standalone.
  4. Sample steering documents — 6 example .kiro/steering/ files covering project standards, git workflow, API design, frontend standards.
  5. Comprehensive process guidespec-process-guide/ tree with methodology, process, AI-reasoning, prompting strategies, examples, and resources.

Attribution

README notes: "Used by @kazini in their spec kit https://github.com/kazini/yask-spec-kit" and "Amazon in internal presentations: 'It's the best stuff I have found on [spec driven development].'"

02

Architecture

kiro (jasonkneen) — Architecture

Distribution

  • Claude Code plugin: .claude-plugin/ (plugin name: kiro-spec-driven, version 1.0.0)
  • MCP server: mcp-server/ (present in repo)
  • Web app example: kiro-web-app/ (present in repo)
  • Language: Markdown (skills, commands, steering), TypeScript (MCP server, web app)
  • MIT license

Install

# As Claude Code plugin (if marketplace-listed):
/plugin install kiro-spec-driven

# Manual:
git clone https://github.com/jasonkneen/kiro.git
cp -r skills/ .claude/skills/
cp -r commands/ .claude/commands/

Directory Tree

.claude-plugin/
  plugin.json         # Claude Code plugin manifest
  marketplace.json    # Marketplace listing metadata

skills/
  README.md
  ai-prompting/
    SKILL.md
  create-steering-documents/
    SKILL.md
  design-documentation/
    SKILL.md
  quality-assurance/
    SKILL.md
  requirements-engineering/
    SKILL.md
  spec-driven-development/
    SKILL.md
  task-breakdown/
    SKILL.md
  troubleshooting/
    SKILL.md

commands/
  create-steering-documents.md
  create-steering-documents-standalone.md

.kiro/
  steering/
    api-design.md
    development-environment.md
    frontend-standards.md
    git-workflow.md
    project-standards.md
    steering-creation-guide.md
  system/
    complete-instructions.md
    capabilities.md
    guidelines.md
    quality-standards.md
    response-style.md
    workflow-patterns.md

spec-process-guide/
  methodology/
  process/
  ai-reasoning/
  prompting/
  execution/
  examples/
  resources/
  templates/
  NAVIGATION.md

mcp-server/
  (TypeScript MCP server source)

kiro-web-app/
  (Web application example)

Target AI Tools

Claude Code (primary), Cursor, VS Code, Windsurf (per SKILL.md compatibility front-matter).

Required Runtime

None — skill pack only; no compilation required.

03

Components

kiro (jasonkneen) — Components

Skills (8, in skills/)

Skill Purpose
spec-driven-development Systematic three-phase approach (requirements → design → tasks); EARS format guidance
requirements-engineering Transform vague feature ideas into clear, testable EARS requirements
design-documentation Create comprehensive technical design documents
task-breakdown Convert design into actionable implementation tasks
ai-prompting Effective communication techniques for AI collaboration
quality-assurance Testing and validation for spec-driven implementations
troubleshooting Common issues and solutions for SDD workflow
create-steering-documents Create and maintain steering documents for AI context

Slash Commands (2)

Command Purpose
create-steering-documents Create steering documents interactively
create-steering-documents-standalone Create steering documents without full workflow context

Kiro System Prompt

File Content
.kiro/system/complete-instructions.md Verbatim Kiro IDE system prompt (identity, capabilities, rules, response style)
.kiro/system/capabilities.md Kiro capability descriptions
.kiro/system/guidelines.md Operational guidelines
.kiro/system/quality-standards.md Quality standards
.kiro/system/response-style.md Response style guide
.kiro/system/workflow-patterns.md Workflow patterns

Example Steering Documents (6)

File Content
api-design.md API design standards and conventions
development-environment.md Dev environment setup and requirements
frontend-standards.md Frontend coding standards
git-workflow.md Git branching and commit conventions
project-standards.md Project-wide standards
steering-creation-guide.md Guide for creating steering documents

Process Guide Documentation

Comprehensive tree in spec-process-guide/: methodology, process (3-phase walkthrough), AI-reasoning (decision frameworks), prompting strategies, execution guide, examples (simple + complex), resources (EARS standards), templates (requirements, design, tasks).

05

Prompts

kiro (jasonkneen) — Prompts

Excerpt 1: Kiro IDE System Prompt (Verbatim Identity Section)

Source: .kiro/system/complete-instructions.md

Prompting technique: Brand voice + identity injection; explicit response-style rules; negative constraints ("never discuss sensitive topics", "write ABSOLUTE MINIMAL amount of code").

# Identity
You are Kiro, an AI assistant and IDE built to assist developers.

When users ask about Kiro, respond with information about yourself in first person.

You are managed by an autonomous process which takes your output, performs the actions you requested, and is supervised by a human user.

You talk like a human, not like a bot. You reflect the user's input style in your responses.

# Response style
- We are knowledgeable. We are not instructive. In order to inspire confidence in the programmers we partner with, we've got to bring our expertise and show we know our Java from our JavaScript. But we show up on their level and speak their language, though never in a way that's condescending or off-putting.
- Be decisive, precise, and clear. Lose the fluff when you can.
- Write only the ABSOLUTE MINIMAL amount of code needed to address the requirement, avoid verbose implementations and any code that doesn't directly contribute to the solution
- Don't bold text
- Don't mention the execution log in your response
- Do not repeat yourself, if you just said you're going to do something, and are doing it again, no need to repeat.

Excerpt 2: spec-driven-development SKILL.md — Three-Phase Protocol with "When to Use" Gate

Source: skills/spec-driven-development/SKILL.md

Prompting technique: Prescriptive phase protocol with explicit "when to use / less suitable" decision gate; EARS format examples with concrete patterns.

## When to Use This Skill

**Ideal scenarios:**
- Complex features with multiple components, integrations, or user interactions
- High-stakes projects where rework costs are significant

**Less suitable:**
- Simple bug fixes with obvious solutions
- Experimental prototypes for rapid iteration

## The Three-Phase Workflow

### Phase 1: Requirements Gathering

**EARS Format Patterns:**
WHEN [event] THEN [system] SHALL [response]
IF [precondition] THEN [system] SHALL [response]

**Example:**
**User Story:** As a new user, I want to create an account, so that I can access personalized features.

**Acceptance Criteria:**
1. WHEN user provides valid email and password THEN system SHALL create new account
2. WHEN user provides existing email THEN system SHALL display "email already registered" error
3. WHEN user provides password shorter than 8 characters THEN system SHALL display "password too short" error
4. WHEN account creation succeeds THEN system SHALL send confirmation email
09

Uniqueness

kiro (jasonkneen) — Uniqueness and Positioning

Differs from Seeds

This is a direct port of the kiro seed's methodology into Claude Code's plugin format. The .kiro/system/complete-instructions.md is the verbatim Kiro IDE system prompt (confirmed by "You are Kiro" identity opening and fsWrite tool references). Compared to cc-sdd (which reimplements the Kiro workflow with 17 skills and autonomous implementation), kiro-jasonkneen ships the source-of-truth system prompt and reference documentation rather than an extended workflow. Compared to superpowers, it has no Iron Law enforcement or hooks — skills are invoked manually. It is closer to Archetype 2 (mirror skills + commands) than Archetype 1 (skills-only).

Distinctive Positioning

  1. Verbatim Kiro system prompt: The only framework in the batch that ships the actual Kiro IDE system prompt verbatim — valuable for teams wanting to emulate Kiro's brand voice and reasoning style in Claude Code.
  2. Comprehensive process guide: spec-process-guide/ is the most complete methodology reference in the batch — covers AI reasoning frameworks, prompting strategies, and EARS standards with detailed examples.
  3. High adoption: 665 stars despite being essentially a methodology port — indicates demand for the Kiro workflow outside of the paid IDE.
  4. Multi-tool compatibility declaration: SKILL.md front-matter explicitly lists compatibility: Claude Code, Cursor, VS Code, Windsurf — broadest declared compatibility in the batch.

Observable Failure Modes

  1. January 2026 last commit: Possibly dormant; Kiro IDE has continued evolving; system prompt may be stale.
  2. No hook-based enforcement: Without hooks, skill invocation is purely manual — users must remember to run requirements-engineering before design-documentation.
  3. MCP server not analyzed in depth: mcp-server/ exists but exact tools unknown; may overlap or conflict with the skill pack.
  4. Identity injection risk: Loading "You are Kiro" identity into Claude Code could confuse the agent's self-model if other plugins also define identity.
04

Workflow

kiro (jasonkneen) — Workflow

Three-Phase Spec Workflow (from spec-driven-development/SKILL.md)

Phase Purpose Artifact
1. Requirements Transform vague idea → clear testable requirements using EARS format requirements.md
2. Design Create comprehensive technical plan design.md
3. Tasks Break design into actionable coding tasks tasks.md

EARS Format (Requirements Notation)

WHEN [event] THEN [system] SHALL [response]
IF [precondition] THEN [system] SHALL [response]
WHEN [event] AND [condition] THEN [system] SHALL [response]

Approval Gates

Gate Type
After requirements freetext-clarify
After design freetext-clarify
After tasks freetext-clarify

Steering Document Workflow

  1. /create-steering-documents — creates steering documents for the project
  2. Steering docs loaded into agent context as "always-on" project memory
  3. Example steering docs provided: api-design.md, git-workflow.md, etc.

When to Use (From SKILL.md)

Ideal scenarios:

  • Complex features with multiple components, integrations, or user interactions
  • High-stakes projects where rework costs are significant
  • Team collaboration requiring shared understanding
  • AI-assisted development where clear structure improves output quality

Less suitable:

  • Simple bug fixes with obvious solutions
  • Experimental prototypes for rapid iteration
  • Time-critical hotfixes requiring immediate action
  • Well-established patterns with minimal ambiguity
06

Memory Context

kiro (jasonkneen) — Memory and Context

State Storage

File-based:

File Content
.kiro/specs/{feature}/requirements.md EARS requirements
.kiro/specs/{feature}/design.md Design document
.kiro/specs/{feature}/tasks.md Task list
.kiro/steering/*.md Project-wide steering context
.kiro/system/*.md Kiro system prompt files

Persistence Level

project — all under .kiro/.

Steering Documents

6 example files covering API design, dev environment, frontend standards, git workflow, project standards, and a steering creation guide. These are templates demonstrating the steering document convention from Kiro IDE.

Cross-Session Handoff

Yes — spec files loaded from disk at session start.

Context Compaction

Not addressed. Skills are invoked on demand and load relevant spec files as needed.

07

Orchestration

kiro (jasonkneen) — Orchestration

Multi-Agent

No.

Orchestration Pattern

sequential — three-phase spec workflow.

Multi-Model

No.

Isolation Mechanism

None.

Execution Mode

one-shot per skill invocation.

Cross-Tool Portability

Medium — targets Claude Code primarily; SKILL.md front-matter lists compatibility: Claude Code, Cursor, VS Code, Windsurf.

08

Ui Cli Surface

kiro (jasonkneen) — UI, CLI, and Surface

CLI Binary

None.

MCP Server

mcp-server/ directory in repo — TypeScript MCP server (exact tools not inspected in depth). This provides an MCP interface to the kiro spec workflow for non-Claude Code clients.

Web App Example

kiro-web-app/ — example web application (not framework tooling; demonstration project).

Claude Code Plugin

.claude-plugin/plugin.json + marketplace.json — packaged as Claude Code plugin for marketplace distribution.

Observability

No audit log. No dashboard.

Related frameworks

same archetype · same primary tool · same memory type

claude-mem (thedotmack) ★ 78k

Background worker service captures every tool call as an observation, AI-compresses sessions, and auto-injects relevant past…

pi (badlogic/earendil) ★ 55k

A minimal, hackable, multi-provider terminal coding agent that adapts to your workflows via npm-installable TypeScript Extensions…

Agent Skills (Addy Osmani) ★ 46k

Encodes senior-engineer software development lifecycle as 23 auto-routed skills and 7 slash commands for any AI coding agent.

wshobson/agents Plugin Marketplace ★ 36k

Single Markdown source for 83 domain-specialized plugins that auto-generates idiomatic artifacts for five AI coding harnesses.

TabbyML/Tabby ★ 34k

Self-hosted AI coding assistant server (alternative to GitHub Copilot) with admin dashboard, RAG-based completions, and multi-IDE…

Compound Engineering ★ 17k

Make each unit of engineering work compound into easier future work via brainstorm→plan→execute→review→learn cycles.