Skip to content

kiro.md

Latest commit

 

History

History
76 lines (59 loc) · 3.42 KB

kiro.md

File metadata and controls

76 lines (59 loc) · 3.42 KB
Raw

Installing deliberation as a Kiro Power

Kiro (AWS) packages reusable tool + steering bundles as Powers. The deliberation Power ships a POWER.md, an mcp.json, and steering/ files at the repo root, all generated by scripts/sync-hosts.js from the canonical sources (AGENTS.md, rules/triggers.md). A Power activates on-demand when its keywords match your task, so the MCP tools load only when a delegation is actually relevant.

Install

In Kiro, use Add power from GitHub and paste this repository URL:

https://github.com/antonbabenko/deliberation

Kiro reads POWER.md (frontmatter + routing guidance), registers the MCP server from mcp.json, and loads the steering/ files. Source: kiro.dev/docs/powers/create.

Provider credentials

The MCP server (npx -y @antonbabenko/deliberation-mcp, stdio) reads provider credentials from the host environment. Set whichever providers you use:

Provider How it authenticates
GPT (Codex) OpenAI / Codex CLI auth (Codex login or OPENAI_API_KEY)
Gemini The Antigravity CLI (agy) - sign in once with the CLI
Grok (xAI) XAI_API_KEY
OpenRouter OPENROUTER_API_KEY (advisory-only; declare models in ~/.config/deliberation/config.json)

mcp.json declares an empty env: {}; the bridges pick the keys up from the process environment Kiro launches the server in. You only need the providers you intend to call - missing keys just disable that one provider.

Activation keywords

The Power loads when your task mentions any of its keywords:

architecture review, security review, second opinion, consensus,
code review, plan review, debug, grok, openrouter, gpt, gemini, deliberation

Once loaded, the steering files tell Kiro when to call each tool (ask-all, consensus, ask-gpt / ask-gemini / ask-grok / ask-openrouter) and each expert persona (architect, plan-reviewer, scope-analyst, code-reviewer, security-analyst, researcher, debugger).

Submitting to the Kiro Powers registry

This Power lives in a public GitHub repo, which is the only prerequisite for the official registry. Submit it at kiro.dev/powers/submit: fill in your name, email, a short use-case description, and the public repository URL. The Kiro team reviews submissions and contacts candidates about registry inclusion. The submission checklist requires that POWER.md carries License (SPDX), a Privacy Policy link, and a Support contact - the generated ## License and support footer satisfies this.

Notes / unverified

  • The official docs (kiro.dev/docs/powers, /create, /powers/submit, /docs/steering) confirm: POWER.md frontmatter fields (name, displayName, description, keywords, author), the root-level mcp.json shape (no type field in Kiro's examples), the steering/ subdirectory, inclusion: always steering frontmatter, the Add power from GitHub install flow, and the License / Privacy / Support footer requirement.
  • [unverified] Whether Kiro reads per-server env substitution like ${VAR} inside a Power's mcp.json (Kiro's example shows ${SUPABASE_URL}, but deliberation reads keys straight from the process env, so we ship env: {}). Confirm at kiro.dev/docs/powers/create if you want to pin keys in mcp.json instead of the environment.