For Kiro IDE users #363
Open
For Kiro IDE users #363
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
all skills was translated for Kiro ide. To use it in Kiro, head over to kiro powers, install it by "add custom power".
added a pull request file and made changes in readme
📝 WalkthroughWalkthroughThis PR adds comprehensive documentation for Superpowers, a software development workflow system for AI-assisted coding. It includes a README, core framework documentation (POWER.md), and seven structured steering guides covering brainstorming, design validation, git worktrees, TDD, code review, subagent-driven development, and systematic debugging. No code changes or API modifications are introduced. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 8
🤖 Fix all issues with AI agents
In @.Kiro/pull request/PULL_REQUEST_TEMPLATE.md:
- Around line 5-75: The PR uses inconsistent casing between ".kiro/" and
".Kiro/" which will break on case-sensitive filesystems; pick one canonical
directory name (recommended ".kiro/"), then update the install instruction
string ("Add Custom Power" using the `.kiro/` directory), the "Files added"
listing, and the POWER.md/README.md references to use that exact casing, or
alternatively rename the actual directory to match the template; ensure the
steering filenames (brainstorming.md, test-driven-development.md, etc.) and
POWER.md are referenced with the same chosen casing throughout.
In @.Kiro/README.md:
- Around line 41-54: The fenced code block starting with triple backticks that
contains the agent/user interaction should include a language identifier; change
the opening ``` to ```text (i.e., add the language label "text") so the block is
properly highlighted and matches the suggested edit, ensuring the block that
begins with You: "I want to build a REST API for managing tasks" is updated
accordingly.
- Around line 7-14: Fix typos and formatting in the install instructions in
.Kiro/README.md: correct misspellings like "intall" -> "install", "how to
install" should have a closing ** to match the opening bold, normalize path
casing to ".Kiro" everywhere (including the explanatory sentence) to avoid
confusion on case-sensitive filesystems, tidy numbering/punctuation (use "1."
etc.), and clarify the example by explicitly instructing users to select the
"Superpower" folder located under ".Kiro".
In @.Kiro/Superpower/POWER.md:
- Around line 78-121: The fenced code blocks in POWER.md lack language
identifiers; update every triple-backtick block (the initial example block
containing "I want to build a user authentication system" and the Example
Workflow blocks including the "User: 'I need a REST API for managing tasks'" and
the agent conversation) to include a language tag (e.g., change ``` to ```text)
so they render with a consistent language identifier; search for the ``` markers
in the file and replace them with ```text for each relevant block.
- Around line 36-56: The documented skill list in POWER.md includes items not
present in the package; update the doc to match the actual shipped skills by
either adding the missing steering skill files for writing-plans,
executing-plans, requesting-code-review, receiving-code-review,
verification-before-completion, root-cause-tracing, defense-in-depth,
finishing-a-development-branch, and dispatching-parallel-agents, or trim
POWER.md to only list the shipped skills (brainstorming, code-review,
subagent-driven-development, systematic-debugging, test-driven-development) — if
trimming, also remove the non-shipped writing-plans entry mentioned in the
comment and ensure the Development Workflow, Quality Assurance, Debugging &
Problem Solving, and Project Management sections only reference existing files.
In @.Kiro/Superpower/steering/brainstorming.md:
- Around line 19-21: Update the bulleted line that currently reads "Prefer
multiple choice questions when possible, but open-ended is fine too" to
hyphenate "multiple-choice" so it reads "Prefer multiple-choice questions when
possible, but open-ended is fine too"; locate this change in
.Kiro/Superpower/steering/brainstorming.md by finding the bullet starting with
"Prefer multiple choice questions" and apply the hyphenation.
In @.Kiro/Superpower/steering/git-worktrees.md:
- Around line 124-128: The workflow list references a non-existent skill symbol
**finishing-a-development-branch**; remove or replace that item in the workflow
integration bullet so the sequence (**brainstorming** → creates design →
**using-git-worktrees** → **writing-plans**) only references valid Kiro steering
skills, and update any links/anchors pointing to
**finishing-a-development-branch** elsewhere in the document to the chosen
existing skill name (or delete those anchors if you remove the step entirely) to
keep the doc consistent.
In @.Kiro/Superpower/steering/systematic-debugging.md:
- Around line 139-142: The document references non-existent skill names
verification-before-completion and requesting-code-review; update the "Use with
other skills" list to only include actual skills from the steering set by either
removing those two entries or replacing them with real skill identifiers found
in .Kiro/Superpower/steering/ (e.g., swap to existing skills such as
test-driven-development and any applicable review or verification skill present
in the directory), and ensure the bullet list is consistent with the
repository's steering skill names.
🧹 Nitpick comments (1)
.Kiro/Superpower/steering/getting-started.md (1)
28-70: Optional: Add language specifier to conversation example code block.The fenced code block containing the conversation example could specify a language for better Markdown compliance and potential syntax highlighting.
♻️ Optional formatting improvement
Add a language specifier to the fenced code block:
-``` +```text You: "I need a user authentication system for my web app"This addresses the markdownlint hint while maintaining clarity.
Comment on lines
+5
to
+75
| To use it in Kiro, head over to Kiro Powers and install it by "Add Custom Power" using the `.kiro/` directory. | ||
|
|
||
| ## Motivation and Context | ||
|
|
||
| Kiro is a popular AI-powered IDE that uses a "Powers" system for extending functionality. This change makes Superpowers available to Kiro users by: | ||
|
|
||
| 1. **Adapting skills to Kiro's steering system** - Converting the original skills to Kiro's steering file format | ||
| 2. **Creating proper power structure** - Adding POWER.md with YAML frontmatter and clean directory structure | ||
| 3. **Maintaining skill functionality** - All core Superpowers workflows (brainstorming, TDD, planning, subagent-driven development, etc.) work identically in Kiro | ||
| 4. **Expanding platform support** - Kiro joins Claude Code, Codex, and OpenCode as supported platforms | ||
|
|
||
| This addresses the gap for Kiro users who want to use the systematic development workflows that Superpowers provides. | ||
|
|
||
| ## How Has This Been Tested? | ||
|
|
||
| - ✅ **Power installation tested** - Successfully imports as Kiro power without validation errors | ||
| - ✅ **Steering files validated** - All 8 core skills load properly in Kiro's steering system | ||
| - ✅ **Workflow integration tested** - Skills activate automatically based on context (brainstorming → planning → TDD → subagent execution) | ||
| - ✅ **Cross-platform compatibility** - Original platform integrations remain unchanged and functional | ||
|
|
||
| **Test scenarios covered:** | ||
| - Power installation via "Add Custom Power" | ||
| - Automatic skill triggering (brainstorming activates when describing features) | ||
| - TDD workflow enforcement (RED-GREEN-REFACTOR cycles) | ||
| - Subagent-driven development with quality reviews | ||
| - Git worktree management for feature isolation | ||
|
|
||
| ## Breaking Changes | ||
|
|
||
| **None.** This is purely additive: | ||
| - All existing platform integrations (Claude Code, Codex, OpenCode) remain unchanged | ||
| - Original skill files in `skills/` directory are untouched | ||
| - No modifications to existing installation or usage patterns | ||
|
|
||
| ## Types of changes | ||
|
|
||
| - [x] New feature (non-breaking change which adds functionality) | ||
| - [ ] Bug fix (non-breaking change which fixes an issue) | ||
| - [ ] Breaking change (fix or feature that would cause existing functionality to change) | ||
| - [x] Documentation update | ||
|
|
||
| ## Checklist | ||
|
|
||
| - [x] My code follows the repository's style guidelines | ||
| - [x] New and existing tests pass locally (no tests broken, Kiro integration is isolated) | ||
| - [x] I have added appropriate error handling (power validation, steering file format compliance) | ||
| - [x] I have added or updated documentation as needed (README updated with Kiro installation instructions) | ||
|
|
||
| ## Additional context | ||
|
|
||
| **Implementation approach:** | ||
| - **Clean separation**: Kiro integration lives in `.kiro/` directory, doesn't interfere with existing platforms | ||
| - **Skill adaptation**: Original skills converted to Kiro steering format with proper YAML frontmatter | ||
| - **Power structure**: Follows Kiro's power specification (POWER.md + steering/*.md files only) | ||
| - **Automatic activation**: Skills trigger based on context, maintaining the "automatic superpowers" philosophy | ||
|
|
||
| **Files added:** | ||
| ``` | ||
| .kiro/ | ||
| ├── POWER.md # Kiro power definition with YAML frontmatter | ||
| ├── README.md # Kiro-specific installation and usage guide | ||
| └── steering/ # Skills adapted for Kiro steering system | ||
| ├── brainstorming.md | ||
| ├── test-driven-development.md | ||
| ├── writing-plans.md | ||
| ├── subagent-driven-development.md | ||
| ├── systematic-debugging.md | ||
| ├── git-worktrees.md | ||
| ├── code-review.md | ||
| └── getting-started.md | ||
| ``` |
There was a problem hiding this comment.
Use consistent .Kiro/ casing in install path and file list.
This template references .kiro/, but the added files are under .Kiro/. On case-sensitive systems that’s a real path mismatch.
✏️ Suggested edit
-To use it in Kiro, head over to Kiro Powers and install it by "Add Custom Power" using the `.kiro/` directory.
+To use it in Kiro, head over to Kiro Powers and install it by "Add Custom Power" using the `.Kiro/` directory.
@@
-.kiro/
+.Kiro/
├── POWER.md # Kiro power definition with YAML frontmatter
├── README.md # Kiro-specific installation and usage guide
└── steering/ # Skills adapted for Kiro steering system🧰 Tools
🪛 LanguageTool
[style] ~42-~42: Consider using a different verb for a more formal wording.
Context: ... [ ] Bug fix (non-breaking change which fixes an issue) - [ ] Breaking change (fix or...
(FIX_RESOLVE)
🤖 Prompt for AI Agents
In @.Kiro/pull request/PULL_REQUEST_TEMPLATE.md around lines 5 - 75, The PR uses
inconsistent casing between ".kiro/" and ".Kiro/" which will break on
case-sensitive filesystems; pick one canonical directory name (recommended
".kiro/"), then update the install instruction string ("Add Custom Power" using
the `.kiro/` directory), the "Files added" listing, and the POWER.md/README.md
references to use that exact casing, or alternatively rename the actual
directory to match the template; ensure the steering filenames
(brainstorming.md, test-driven-development.md, etc.) and POWER.md are referenced
with the same chosen casing throughout.
Comment on lines
+7
to
+14
| This power is designed to be installed in Kiro's power system. Once installed, all steering files will be automatically loaded and the skills will activate based on context. | ||
| - **how to install** - | ||
| 1, head over to kiro powers. | ||
| 2, intall it by "add custom power" | ||
| 3, Import power from a folder | ||
| 4, select the root (for example): "C:\superpowers\.Kiro\Superpower" | ||
| **Important, make sure to select the "Superpower" folder located under ".kiro" | ||
|
|
There was a problem hiding this comment.
Fix typos + path casing in install steps (and close the bold).
Spelling errors and .kiro vs .Kiro casing can mislead users (especially on case-sensitive filesystems), and the bold sentence is missing its closing **.
✏️ Suggested edit
-This power is designed to be installed in Kiro's power system. Once installed, all steering files will be automatically loaded and the skills will activate based on context.
-- **how to install** -
-1, head over to kiro powers.
-2, intall it by "add custom power"
-3, Import power from a folder
-4, select the root (for example): "C:\superpowers\.Kiro\Superpower"
-**Important, make sure to select the "Superpower" folder located under ".kiro"
+This power is designed to be installed in Kiro's power system. Once installed, all steering files will be automatically loaded and the skills will activate based on context.
+- **How to install**
+1. Head over to Kiro Powers.
+2. Install it by selecting **Add Custom Power**.
+3. Import power from a folder.
+4. Select the root (for example): `C:\superpowers\.Kiro\Superpower`
+**Important:** Make sure to select the **Superpower** folder located under `.Kiro`.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| This power is designed to be installed in Kiro's power system. Once installed, all steering files will be automatically loaded and the skills will activate based on context. | |
| - **how to install** - | |
| 1, head over to kiro powers. | |
| 2, intall it by "add custom power" | |
| 3, Import power from a folder | |
| 4, select the root (for example): "C:\superpowers\.Kiro\Superpower" | |
| **Important, make sure to select the "Superpower" folder located under ".kiro" | |
| This power is designed to be installed in Kiro's power system. Once installed, all steering files will be automatically loaded and the skills will activate based on context. | |
| - **How to install** | |
| 1. Head over to Kiro Powers. | |
| 2. Install it by selecting **Add Custom Power**. | |
| 3. Import power from a folder. | |
| 4. Select the root (for example): `C:\superpowers\.Kiro\Superpower` | |
| **Important:** Make sure to select the **Superpower** folder located under `.Kiro`. |
🤖 Prompt for AI Agents
In @.Kiro/README.md around lines 7 - 14, Fix typos and formatting in the install
instructions in .Kiro/README.md: correct misspellings like "intall" ->
"install", "how to install" should have a closing ** to match the opening bold,
normalize path casing to ".Kiro" everywhere (including the explanatory sentence)
to avoid confusion on case-sensitive filesystems, tidy numbering/punctuation
(use "1." etc.), and clarify the example by explicitly instructing users to
select the "Superpower" folder located under ".Kiro".
Comment on lines
+41
to
+54
| ``` | ||
| You: "I want to build a REST API for managing tasks" | ||
|
|
||
| Agent: [brainstorming skill activates automatically] | ||
| "Let me understand what you're building. What kind of tasks will this manage?" | ||
| [continues with systematic requirements gathering] | ||
|
|
||
| Agent: [presents design in reviewable sections] | ||
| "Here's the API design so far..." | ||
|
|
||
| Agent: [creates git worktree for isolated development] | ||
| Agent: [writes detailed implementation plan] | ||
| Agent: [executes with subagents using TDD] | ||
| ``` |
There was a problem hiding this comment.
Add a language to the fenced code block.
✏️ Suggested edit
-```
+```text
You: "I want to build a REST API for managing tasks"
Agent: [brainstorming skill activates automatically]
"Let me understand what you're building. What kind of tasks will this manage?"
[continues with systematic requirements gathering]
Agent: [presents design in reviewable sections]
"Here's the API design so far..."
Agent: [creates git worktree for isolated development]
Agent: [writes detailed implementation plan]
Agent: [executes with subagents using TDD]</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
41-41: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In @.Kiro/README.md around lines 41 - 54, The fenced code block starting with
triple backticks that contains the agent/user interaction should include a
language identifier; change the opening ``` to ```text (i.e., add the language
label "text") so the block is properly highlighted and matches the suggested
edit, ensuring the block that begins with You: "I want to build a REST API for
managing tasks" is updated accordingly.
Comment on lines
+36
to
+56
| ### Development Workflow | ||
| - **brainstorming** - Interactive design refinement before coding | ||
| - **writing-plans** - Detailed implementation plans with exact steps | ||
| - **executing-plans** - Batch execution with human checkpoints | ||
| - **subagent-driven-development** - Fresh subagents per task with reviews | ||
|
|
||
| ### Quality Assurance | ||
| - **test-driven-development** - Strict RED-GREEN-REFACTOR enforcement | ||
| - **requesting-code-review** - Pre-review checklists and systematic reviews | ||
| - **receiving-code-review** - Structured feedback response | ||
| - **verification-before-completion** - Ensure fixes actually work | ||
|
|
||
| ### Debugging & Problem Solving | ||
| - **systematic-debugging** - 4-phase root cause analysis | ||
| - **root-cause-tracing** - Deep investigation techniques | ||
| - **defense-in-depth** - Robust error handling patterns | ||
|
|
||
| ### Project Management | ||
| - **using-git-worktrees** - Parallel development branches | ||
| - **finishing-a-development-branch** - Merge/PR decision workflows | ||
| - **dispatching-parallel-agents** - Concurrent subagent workflows |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# List files in the steering directory
echo "=== Files in .Kiro/Superpower/steering/ ==="
fd -t f . .Kiro/Superpower/steering/ 2>/dev/null | sort
echo ""
echo "=== Directory structure ==="
tree .Kiro/Superpower/steering/ 2>/dev/null || find .Kiro/Superpower/steering/ -type f 2>/dev/null | head -30Repository: obra/superpowers
Length of output: 691
🏁 Script executed:
#!/bin/bash
# Check the exact lines 36-56 in POWER.md to see the documented skills
echo "=== Content of POWER.md lines 36-56 ==="
sed -n '36,56p' .Kiro/Superpower/POWER.mdRepository: obra/superpowers
Length of output: 1108
Skill list includes items not shipped in the Kiro package.
The documentation names 14 skills across these categories, but only 5 are actually shipped in .Kiro/Superpower/steering/: brainstorming, code-review, subagent-driven-development, systematic-debugging, and test-driven-development. The following skills are documented but missing:
- Development Workflow: writing-plans, executing-plans
- Quality Assurance: requesting-code-review, receiving-code-review, verification-before-completion
- Debugging & Problem Solving: root-cause-tracing, defense-in-depth
- Project Management: finishing-a-development-branch, dispatching-parallel-agents
This mismatch will mislead users about what's actually included. Either add the missing skill files or trim this list to only the shipped ones. Note: The suggested diff still retains writing-plans despite it not being shipped; that should also be removed if trimming.
🤖 Prompt for AI Agents
In @.Kiro/Superpower/POWER.md around lines 36 - 56, The documented skill list in
POWER.md includes items not present in the package; update the doc to match the
actual shipped skills by either adding the missing steering skill files for
writing-plans, executing-plans, requesting-code-review, receiving-code-review,
verification-before-completion, root-cause-tracing, defense-in-depth,
finishing-a-development-branch, and dispatching-parallel-agents, or trim
POWER.md to only list the shipped skills (brainstorming, code-review,
subagent-driven-development, systematic-debugging, test-driven-development) — if
trimming, also remove the non-shipped writing-plans entry mentioned in the
comment and ensure the Development Workflow, Quality Assurance, Debugging &
Problem Solving, and Project Management sections only reference existing files.
Comment on lines
+78
to
+121
| ``` | ||
| "I want to build a user authentication system" | ||
| ``` | ||
|
|
||
| The agent will automatically: | ||
| 1. Use **brainstorming** to refine requirements | ||
| 2. Use **writing-plans** to create implementation steps | ||
| 3. Use **subagent-driven-development** to execute with quality reviews | ||
| 4. Follow **test-driven-development** throughout | ||
| 5. Use **finishing-a-development-branch** when complete | ||
|
|
||
| ## Example Workflow | ||
|
|
||
| ``` | ||
| User: "I need a REST API for managing tasks" | ||
|
|
||
| Agent: [brainstorming skill activates] | ||
| "Let me understand what you're building. What kind of tasks will this manage? | ||
| Personal todos, project tasks, or something else?" | ||
|
|
||
| User: "Project tasks for a team" | ||
|
|
||
| Agent: "Got it. Should this integrate with existing auth, or handle its own users?" | ||
| [continues refining through questions] | ||
|
|
||
| Agent: [presents design in sections] | ||
| "Here's the API design so far: | ||
| - Task CRUD operations (create, read, update, delete) | ||
| - Team membership and permissions | ||
| - Task assignment and status tracking | ||
| Does this look right?" | ||
|
|
||
| User: "Yes, but add due dates and priorities" | ||
|
|
||
| Agent: [writing-plans skill activates] | ||
| "I'm creating the implementation plan..." | ||
| [saves detailed plan to docs/plans/2025-01-26-task-api-implementation.md] | ||
|
|
||
| Agent: [subagent-driven-development activates] | ||
| "Executing plan with subagents..." | ||
| [dispatches implementer subagent for each task] | ||
| [runs spec compliance and code quality reviews] | ||
| [continues autonomously for hours] | ||
| ``` |
There was a problem hiding this comment.
Add language identifiers to fenced code blocks.
✏️ Suggested edit
-```
+```text
"I want to build a user authentication system"@@
- +text
User: "I need a REST API for managing tasks"
@@
[continues autonomously for hours]
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
78-78: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
91-91: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In @.Kiro/Superpower/POWER.md around lines 78 - 121, The fenced code blocks in
POWER.md lack language identifiers; update every triple-backtick block (the
initial example block containing "I want to build a user authentication system"
and the Example Workflow blocks including the "User: 'I need a REST API for
managing tasks'" and the agent conversation) to include a language tag (e.g.,
change ``` to ```text) so they render with a consistent language identifier;
search for the ``` markers in the file and replace them with ```text for each
relevant block.
Comment on lines
+19
to
+21
| - Ask questions one at a time to refine the idea | ||
| - Prefer multiple choice questions when possible, but open-ended is fine too | ||
| - Only one question per message - if a topic needs more exploration, break it into multiple questions |
There was a problem hiding this comment.
Hyphenate “multiple-choice”.
✏️ Suggested edit
-- Prefer multiple choice questions when possible, but open-ended is fine too
+-- Prefer multiple-choice questions when possible, but open-ended is fine too📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| - Ask questions one at a time to refine the idea | |
| - Prefer multiple choice questions when possible, but open-ended is fine too | |
| - Only one question per message - if a topic needs more exploration, break it into multiple questions | |
| - Ask questions one at a time to refine the idea | |
| - Prefer multiple-choice questions when possible, but open-ended is fine too | |
| - Only one question per message - if a topic needs more exploration, break it into multiple questions |
🧰 Tools
🪛 LanguageTool
[grammar] ~20-~20: Use a hyphen to join words.
Context: ...ime to refine the idea - Prefer multiple choice questions when possible, but open...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
In @.Kiro/Superpower/steering/brainstorming.md around lines 19 - 21, Update the
bulleted line that currently reads "Prefer multiple choice questions when
possible, but open-ended is fine too" to hyphenate "multiple-choice" so it reads
"Prefer multiple-choice questions when possible, but open-ended is fine too";
locate this change in .Kiro/Superpower/steering/brainstorming.md by finding the
bullet starting with "Prefer multiple choice questions" and apply the
hyphenation.
Comment on lines
+124
to
+128
| **Workflow integration:** | ||
| - **brainstorming** → creates design → **using-git-worktrees** → **writing-plans** | ||
| - Use after design approval, before implementation planning | ||
| - Provides clean workspace for **test-driven-development** | ||
| - Enables **finishing-a-development-branch** workflow No newline at end of file |
There was a problem hiding this comment.
Remove/replace references to non-existent skills.
finishing-a-development-branch isn’t part of the Kiro steering set in this PR. Consider removing it or mapping to an existing skill to avoid confusion.
✏️ Suggested edit
-- Enables **finishing-a-development-branch** workflow
+- Enables clean review and merge prep before **code-review**📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| **Workflow integration:** | |
| - **brainstorming** → creates design → **using-git-worktrees** → **writing-plans** | |
| - Use after design approval, before implementation planning | |
| - Provides clean workspace for **test-driven-development** | |
| - Enables **finishing-a-development-branch** workflow | |
| **Workflow integration:** | |
| - **brainstorming** → creates design → **using-git-worktrees** → **writing-plans** | |
| - Use after design approval, before implementation planning | |
| - Provides clean workspace for **test-driven-development** | |
| - Enables clean review and merge prep before **code-review** |
🤖 Prompt for AI Agents
In @.Kiro/Superpower/steering/git-worktrees.md around lines 124 - 128, The
workflow list references a non-existent skill symbol
**finishing-a-development-branch**; remove or replace that item in the workflow
integration bullet so the sequence (**brainstorming** → creates design →
**using-git-worktrees** → **writing-plans**) only references valid Kiro steering
skills, and update any links/anchors pointing to
**finishing-a-development-branch** elsewhere in the document to the chosen
existing skill name (or delete those anchors if you remove the step entirely) to
keep the doc consistent.
Comment on lines
+139
to
+142
| **Use with other skills:** | ||
| - **test-driven-development** - Write failing test for bug before fixing | ||
| - **verification-before-completion** - Ensure fix actually works | ||
| - **requesting-code-review** - Get second pair of eyes on fix No newline at end of file |
There was a problem hiding this comment.
Align integration references with actual Kiro skills.
This section points to verification-before-completion and requesting-code-review, which don’t appear in the Kiro steering set listed in this PR. Consider removing or replacing them with skills that exist in .Kiro/Superpower/steering/ to avoid broken expectations.
💡 Suggested edit
- - **verification-before-completion** - Ensure fix actually works
- - **requesting-code-review** - Get second pair of eyes on fix
+ - **test-driven-development** - Write failing test for bug before fixing
+ - **code-review** - Get second pair of eyes on fix🤖 Prompt for AI Agents
In @.Kiro/Superpower/steering/systematic-debugging.md around lines 139 - 142,
The document references non-existent skill names verification-before-completion
and requesting-code-review; update the "Use with other skills" list to only
include actual skills from the steering set by either removing those two entries
or replacing them with real skill identifiers found in
.Kiro/Superpower/steering/ (e.g., swap to existing skills such as
test-driven-development and any applicable review or verification skill present
in the directory), and ensure the bullet list is consistent with the
repository's steering skill names.
paseka10jaroslav-coder
approved these changes
Jan 26, 2026
paseka10jaroslav-coder
approved these changes
Jan 26, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Kiro IDE Support for Superpowers
All skills have been translated and adapted for Kiro IDE. This adds native Kiro power support alongside the existing Claude Code, Codex, and OpenCode integrations.
To use it in Kiro, head over to Kiro Powers and install it by "Add Custom Power" using the
.kiro/directory.Motivation and Context
Kiro is a popular AI-powered IDE that uses a "Powers" system for extending functionality. This change makes Superpowers available to Kiro users by:
This addresses the gap for Kiro users who want to use the systematic development workflows that Superpowers provides.
How Has This Been Tested?
Test scenarios covered:
Breaking Changes
None. This is purely additive:
skills/directory are untouchedTypes of changes
Checklist
Additional context
Implementation approach:
.kiro/directory, doesn't interfere with existing platformsFiles added:
Design decisions:
inclusion: alwaysto maintain automatic triggering behaviorinclusion: manualso users can access it via#getting-startedwhen neededThis maintains Superpowers' core value proposition - systematic, test-driven development workflows - while making it accessible to Kiro's growing user base.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.