[PR #69] [MERGED] feat: add kiro power config #214

New issue

Closed

opened 2026-03-15 11:53:40 +03:00 by kerem · 0 comments

kerem commented

2026-03-15 11:53:40 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/awslabs/iam-policy-autopilot/pull/69
Author: @hwei0
Created: 12/11/2025
Status: ✅ Merged
Merged: 12/17/2025
Merged by: @hwei0

Base: main ← Head: main

📝 Commits (2)

3347e34 feat: add kiro power config
dcfb721 Merge branch 'main' into main

📊 Changes

3 files changed (+87 additions, -0 deletions)

View changed files

📝 README.md (+28 -0)
➕ power-iam-policy-autopilot/POWER.md (+48 -0)
➕ power-iam-policy-autopilot/mcp.json (+11 -0)

📄 Description

Issue #, if available:
https://github.com/awslabs/iam-policy-autopilot/issues/64
Description of changes:
Adding a kiro power configuration directory, consisting of:

a POWER.md readme, specifying onboarding information and very brief "steering" information (specifically, two example use cases)
a mcp.json config.

(note: in our installation guide we specify two different mcp.json configs, one for pip+binary installation, and one for uv. Kiro powers don't seem to support selectively picking/enabling one mcp.json config out of multiple configs, so I specified in the Kiro power's onboarding doc that the agent must run uv tool install iam-policy-autopilot if it detects a uv-based installation.)

Testing: installed it into my Kiro IDE.

(note: Kiro offers a feature where kiro power can be automatically detected and installed from github repositories, but this functionality seems to be broken. So for now it seems that the power must be installed by doing git clone and installing from a local folder; I specified this as the way to go in the README).

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/awslabs/iam-policy-autopilot/pull/69 **Author:** [@hwei0](https://github.com/hwei0) **Created:** 12/11/2025 **Status:** ✅ Merged **Merged:** 12/17/2025 **Merged by:** [@hwei0](https://github.com/hwei0) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (2) - [`3347e34`](https://github.com/awslabs/iam-policy-autopilot/commit/3347e34481accc529b5cee3fac688cc37301f1a0) feat: add kiro power config - [`dcfb721`](https://github.com/awslabs/iam-policy-autopilot/commit/dcfb721c75a8b8410605eb0c946bef82ab177a34) Merge branch 'main' into main ### 📊 Changes **3 files changed** (+87 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+28 -0) ➕ `power-iam-policy-autopilot/POWER.md` (+48 -0) ➕ `power-iam-policy-autopilot/mcp.json` (+11 -0) </details> ### 📄 Description *Issue #, if available:* https://github.com/awslabs/iam-policy-autopilot/issues/64 *Description of changes:* Adding a kiro power configuration directory, consisting of: 1. a `POWER.md` readme, specifying onboarding information and very brief "steering" information (specifically, two example use cases) 2. a `mcp.json` config. (note: in our installation guide we specify two different `mcp.json` configs, one for pip+binary installation, and one for `uv`. Kiro powers don't seem to support selectively picking/enabling one `mcp.json` config out of multiple configs, so I specified in the Kiro power's onboarding doc that the agent must run `uv tool install iam-policy-autopilot` if it detects a `uv`-based installation.) *Testing*: installed it into my Kiro IDE. (note: Kiro offers a feature where kiro power can be automatically detected and installed from github repositories, but this functionality seems to be broken. So for now it seems that the power must be installed by doing `git clone` and installing from a local folder; I specified this as the way to go in the README). By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>