Skip to content

Add Kiro CLI support#1216

Closed
sigent-ai-dev wants to merge 44 commits into
github:mainfrom
sigent-ai-dev:feature/kiro-cli-support
Closed

Add Kiro CLI support#1216
sigent-ai-dev wants to merge 44 commits into
github:mainfrom
sigent-ai-dev:feature/kiro-cli-support

Conversation

@sigent-ai-dev

@sigent-ai-dev sigent-ai-dev commented Nov 19, 2025

Copy link
Copy Markdown
Contributor

Add Kiro CLI Support

This PR adds support for Kiro CLI, an upgrade replacement for Amazon Q Developer CLI that provides full custom prompt support.

Changes

  • Added Kiro CLI to AGENT_CONFIG in src/specify_cli/init.py

  • Updated release package script (.github/workflows/scripts/create-release-packages.sh)

    • Added kiro to ALL_AGENTS array
    • Added case statement to generate Kiro command files in .kiro/prompts/ directory
    • Uses Markdown format with $ARGUMENTS placeholder
  • Updated documentation (README.md)

    • Added Kiro CLI to Supported AI Agents table with full support (✅)
    • Noted as "Upgrade replacement for Amazon Q Developer CLI with full custom prompt support"
    • Updated CLI tool check documentation to mention Kiro CLI

Related Issues

Addresses the need for better Amazon Q Developer CLI alternative with full custom argument support.

@sigent-ai-dev sigent-ai-dev force-pushed the feature/kiro-cli-support branch from 323ff26 to e588580 Compare November 19, 2025 09:34
@sigent-ai-dev sigent-ai-dev marked this pull request as ready for review November 19, 2025 09:49
@localden localden self-assigned this Dec 2, 2025
@localden localden added merge-candidate Reasonable change that is going to be merged after a review. new-agent labels Dec 2, 2025
@localden

localden commented Dec 2, 2025

Copy link
Copy Markdown
Contributor

@sigent-amazon can you please resolve the conflicts? Once done, happy to merge.

anchildress1 and others added 8 commits December 3, 2025 10:04
- Remove link to non-existent existing project guide from README

Commit-generated-by: GitHub Copilot <github.copilot@github.com>
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
- Remove outdated links section from docs/upgrading-spec-kit.md
- Remove outdated section from README and docs/index

Commit-generated-by: GitHub Copilot <github.copilot@github.com>
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
- Rename docs/upgrading-spec-kit.md to docs/upgrade.md for brevity
- Update README and documentation index links to point to new upgrade guide
- Update table of contents to use shorter "Upgrade" title
- Simplify section headers in upgrade guide
- Add Getting Started section back to docs/index.md with upgrade guide link

Commit-generated-by: GitHub Copilot <github.copilot@github.com>
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
- Fix broken constitution.md link in detailed process section
- Add reference to supported AI agents list in upgrade guide

Commit-generated-by: GitHub Copilot <github.copilot@github.com>
Signed-off-by: Ashley Childress <6563688+anchildress1@users.noreply.github.com>
Kiro CLI (https://kiro.dev) is an upgrade replacement for Amazon Q Developer CLI
with full custom prompt support.

Changes:
- Added 'kiro' to AGENT_CONFIG with .kiro/ folder structure
- Updated CLI help text to include kiro option
- Added Kiro CLI to README supported agents table
- Updated release script to generate Kiro packages
- Kiro uses .kiro/prompts/ directory (markdown format)

Kiro CLI provides the same functionality as Q Developer CLI but with
proper support for custom arguments in slash commands.
@sigent-ai-dev sigent-ai-dev force-pushed the feature/kiro-cli-support branch from 2cd4849 to a1df4aa Compare December 3, 2025 10:04
- Added Kiro CLI support alongside new upstream agents (Qoder, IBM Bob, Jules)
- Resolved conflicts in README.md, AGENTS.md, and all configuration files
- Updated all release scripts to include Kiro CLI packages
- Added Kiro CLI to agent context update scripts (bash and PowerShell)
- Maintained alphabetical ordering in agent lists
- Preserved all upstream improvements and bug fixes
@sigent-ai-dev

Copy link
Copy Markdown
Contributor Author

@localden Conflicts are fixed. Please merge and thank you

@watany-dev

Copy link
Copy Markdown

@sigent-amazon
Looking at the kiro cli documentation, it still seems that local and global do not support arguments. Does it really work?

https://kiro.dev/docs/cli/chat/manage-prompts/#passing-arguments-to-mcp-prompts

MCP server prompts can accept arguments to customize their behavior. File-based prompts (local and global) do not support arguments.

@sigent-ai-dev

Copy link
Copy Markdown
Contributor Author

Apologies - holiday period is crazy.
Yes it works @localden and I'm using it on a current project. I was also using Amazon Q Dev before to. I've seen it twice say it couldn't use the arguments across multiple users / projects. After the first pushback the llm infers the arguments field and it "just works".

@Kalletal

Kalletal commented Jan 14, 2026

Copy link
Copy Markdown

J'ai testé ton code, et "Kiro code" n'apparait pas dans la liste des assistants IA disponible, quand on lance l'init

@sigent-ai-dev

Copy link
Copy Markdown
Contributor Author

@Kalletal Please can you help me understand where it's missing. I see
███████╗██████╗ ███████╗ ██████╗██╗███████╗██╗ ██╗
██╔════╝██╔══██╗██╔════╝██╔════╝██║██╔════╝╚██╗ ██╔╝
███████╗██████╔╝█████╗ ██║ ██║█████╗ ╚████╔╝
╚════██║██╔═══╝ ██╔══╝ ██║ ██║██╔══╝ ╚██╔╝
███████║██║ ███████╗╚██████╗██║██║ ██║
╚══════╝╚═╝ ╚══════╝ ╚═════╝╚═╝╚═╝ ╚═╝

                                                                                           GitHub Spec Kit - Spec-Driven Development Toolkit                                                                                               

╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Specify Project Setup │
│ │
│ Project test-init │
│ Working Path /private/tmp │
│ Target Path /private/tmp/test-init │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

╭───────────────────────────────────────────────────────────────────────────────────────────────────────── Choose your AI assistant: ─────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ copilot (GitHub Copilot) │
│ claude (Claude Code) │
│ gemini (Gemini CLI) │
│ cursor-agent (Cursor) │
│ qwen (Qwen Code) │
│ opencode (opencode) │
│ ▶ codex (Codex CLI) │
│ windsurf (Windsurf) │
│ kilocode (Kilo Code) │
│ auggie (Auggie CLI) │
│ codebuddy (CodeBuddy) │
│ qoder (Qoder CLI) │
│ roo (Roo Code) │
│ q (Amazon Q Developer CLI) │
│ amp (Amp) │
│ kiro (Kiro CLI) │
│ shai (SHAI) │
│ bob (IBM Bob) │
│ │
│ Use ↑/↓ to navigate, Enter to select, Esc to cancel │

@Kalletal

Copy link
Copy Markdown

Si tu executes ton code avec : uvx --from git+https://github.com/sigent-amazon/spec-kit.git specify init test
Kiro n'est pas dans la liste.
J'avais commencé à coder un autre assistant et j'avais pris modèle sur les commit pour l'ajout de SHAI, mais je ne sais pas si c'est bien la méthode à utiliser.
Le mieux c'est de savoir ce qu'on fait :-)
Après tu peux peut être prendre modèle sur les changements qui avait été fait pour l'implémentation d'Amazon Q Developer CLI : https://github.com/github/spec-kit/pull/695/files
Je ne suis pas developpeur non plus :-s malheureusement.

@sigent-ai-dev

Copy link
Copy Markdown
Contributor Author

@Kalletal Kiro support exists only in the feature/kiro-cli-support branch and has not been merged to main yet.

When someone installs from the main branch or from a release:
bash
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git
Which I think is the same as you are doing and you get the main branch, which doesn't have Kiro support.

Kiro doesn't appear in the list because:

  1. Kiro support is only in the feature branch
  2. It hasn't been merged to main
  3. No release has been cut with Kiro support

To get Kiro support, you would need to install from the feature branch:
bash
uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@feature/kiro-cli-support

@Kalletal

Copy link
Copy Markdown

Non ça ne fonctionne pas :

jle@SMI-LP-GDL-01:~/dev$ uvx --from git+https://github.com/github/spec-kit.git@feature/kiro-cli-support specify init test Updating https://github.com/github/spec-kit.git (feature/kiro-cli-support) × Failed to resolve --with` requirement
╰─▶ Git operation failed

jle@SMI-LP-GDL-01: ~/dev$ uv tool install specify-cli --from git+https://github.com/github/spec-kit.git@feature/kiro-cli-support
Updating https://github.com/github/spec-kit.git (feature/kiro-cli-support) error: Git operation failed
Caused by: failed to fetch into: /home/jle/.cache/uv/git-v0/db/0b2d89e6cfcd4f8e
Caused by: failed to fetch branch or tag feature/kiro-cli-support
Caused by: process didn't exit successfully: /usr/bin/git fetch --force --update-head-ok 'https://github.com/github/spec-kit.git' '+refs/tags/feature/kiro-cli-support:refs/remotes/origin/tags/feature/kiro-cli-support' (exit status: 128)
--- stderr
fatal: couldn't find remote ref refs/tags/feature/kiro-cli-support`

@sigent-ai-dev

Copy link
Copy Markdown
Contributor Author

Apologies @Kalletal it should be uv tool install specify-cli --from git+https://github.com/sigent-amazon/spec-kit.git@feature/kiro-cli-support

@Kalletal

Copy link
Copy Markdown

L'installation fonctionne bien cette fois, par contre, spec-kit ne détecte pas l'installation de kiro-cli alors qu'il est installé.

image

@Kalletal

Copy link
Copy Markdown

Si je fais un --ignore-agent-tools j'ai:

image

@sigent-ai-dev

Copy link
Copy Markdown
Contributor Author

hi @Kalletal
Unfortunately, that's expected because it's not been merged to main so there's not a release that will include it. @localden might know of a way to manage this, I have been manually running this step to test

@Kalletal

Copy link
Copy Markdown

Tu pourrais me donner les étapes à effectuer ? please :)

@sigent-ai-dev

Copy link
Copy Markdown
Contributor Author

@Kalletal unfortunately the only way I've found to do this is to update my locally branch and change the download_template_from_github method. Merging the branch will put it in the releases so you wouldn't need to do this step but I'm not a project owner so required @localden or someone else on the team to approve the request of help with a work around

@sigent-ai-dev

Copy link
Copy Markdown
Contributor Author

@Kalletal as a workaround. I've created a https://github.com/sigent-amazon/mcp-spec-kit-kiro-cli
This enables you to create the prompts. If you then run specify init with q and have this mcp running (globally or locally) you'll be able to use speckit with kiro cli now.
Please note the readme that you need to pass arguments in quotes.
@localden it would be good to get your thoughts on this approach?

@Kalletal

Kalletal commented Feb 6, 2026

Copy link
Copy Markdown

C'est dommage que personne ne s'y interesse.

@mnriem mnriem removed the request for review from localden February 27, 2026 14:53
@mnriem

mnriem commented Jun 25, 2026

Copy link
Copy Markdown
Collaborator

Closing as superseded — Kiro CLI is now supported natively (the kiro_cli integration was added via the plugin-architecture migration in #2038), available with specify init --ai kiro-cli. Thank you for the contribution and for helping drive Kiro support! 🙏

@mnriem mnriem closed this Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge-candidate Reasonable change that is going to be merged after a review. new-agent

Projects

None yet

Development

Successfully merging this pull request may close these issues.