Add Kiro Power Support and Installation Instructions#52
Add Kiro Power Support and Installation Instructions#52osataken wants to merge 4 commits intoawslabs:mainfrom
Conversation
- Add variable system for RULE_LOADER_TOOL and RULE_FILE_PATH - Support Amazon Q Developer, Kiro CLI, and Kiro Power platforms - Update all rule loading references to use platform variables - Add platform detection logic with priority order - Document file loading examples for each platform
- Add POWER.md with metadata and complete documentation - Add README.md with multi-platform installation instructions - Include shell commands for Linux/macOS and Windows - Document power structure and verification steps - Add troubleshooting guide for common issues
- Link to Kiro Power installation guide in Quick Start section - Position after Kiro CLI section for logical flow
There was a problem hiding this comment.
Can we build this in a way that we programmatically copy over or reuse the main README.md (or parts of it) in this directory instead of duplicating its contents here. That way any changes in the main README.md will be updated in Kiro POWER.md automatically and we won't have to maintain two separate files with duplicated content. We foresee major changes in the steering files structure to address the systemic over-bloating issues, so reusing original content will be highly beneficial.
There was a problem hiding this comment.
Yes, we can combine the install instruction into single README. I originally created a separated file to minimize the changes on the core-workflow artifacts as Kiro Power is quite specific to Kiro only.
| mkdir -p .kiro/powers/ai-dlc-methodology/steering | ||
| cp ../aidlc-workflows/aidlc-kiro-power/POWER.md .kiro/powers/ai-dlc-methodology/ | ||
| cp ../aidlc-workflows/aidlc-rules/aws-aidlc-rules/core-workflow.md .kiro/powers/ai-dlc-methodology/steering/ | ||
| cp ../aidlc-workflows/aidlc-rules/aws-aidlc-rule-details/common/*.md .kiro/powers/ai-dlc-methodology/steering/ |
There was a problem hiding this comment.
Is it possible to maintain the sub-directories and file arrangements in common, inception etc, as opposed to flattening that directory structure?
There was a problem hiding this comment.
With the current limitations of Kiro Power, we need to flatten the folder for now.
This will be for the first time installation only (from local file). Once the AIDLC Kiro Power got approved and goes to official Kiro Market place, installation will be much easier.
Kiro will use internal command "readSteering" to read the related rule/steering files. Currently, this command doesn't support nested files/folder structure.
There is also another Kiro internal command "readFile" but this command will work only the files located in current workspace. When we install Kiro power, the files will be copied to global installation folder (only the files under steering folder). Using "readFile" command will cause permission error.
| ``` | ||
|
|
||
| **Windows (PowerShell or Command Prompt):** | ||
| ```powershell |
There was a problem hiding this comment.
If we're able to maintain the original directory structure then we won't need so many commands and avoid the human error in missing a command. If we can't do that (because of Kiro power limitation) then suggest we wrap these multiple commands in a script so that the user has to issue a single command and there is no risk of human omission of a command.
There was a problem hiding this comment.
Copied comments from previous one
With the current limitations of Kiro Power, we need to flatten the folder for now.
This will be for the first time installation only (from local file). Once the AIDLC Kiro Power got approved and goes to official Kiro Market place, installation will be much easier.
Kiro will use internal command "readSteering" to read the related rule/steering files. Currently, this command doesn't support nested files/folder structure.
There is also another Kiro internal command "readFile" but this command will work only the files located in current workspace. When we install Kiro power, the files will be copied to global installation folder (only the files under steering folder). Using "readFile" command will cause permission error.
aidlc-kiro-power/README.md
Outdated
| - Look for "AI-DLC Methodology" in the Powers Panel | ||
| - Click to view details and available steering files | ||
|
|
||
| ### Option 2: Global Installation (Shell Script) |
There was a problem hiding this comment.
If we wrapped this in a script then the script can ask the user question at the top - global versus project and then can copy material to right folders automatically.
There was a problem hiding this comment.
Actually, both installation methods will goes to global installation.
The first approach is to copy/flatten the files/folder structure, then install via IDE.
The second approach will just run the script to copy the files to Kiro global installation folder.
I believe that we could remove the second approach to avoid confusion and simplify the installation process.
| ai-dlc-methodology/ | ||
| ├── POWER.md # Main power documentation | ||
| └── steering/ # Detailed workflow rules (flattened structure) | ||
| ├── core-workflow.md # Main workflow orchestration |
There was a problem hiding this comment.
Suggest avoid enumerating the files list here as this will constantly be changing and this information will become obsolete quickly.
There was a problem hiding this comment.
Will try to use files/folder structure definitions on core-workflow instead
|
|
||
| ### For Amazon Q Developer: | ||
| ``` | ||
| RULE_LOADER_TOOL = "readFile" |
There was a problem hiding this comment.
Are these environment variables? If so, should there be export keywords mentioned for Linux/MacOS and equivalent for Windows. Could these be wrapped in the script idea mentioned above?
There was a problem hiding this comment.
No, it is just an internal variable for Kiro/Amazon Q Dev/other AI agents to use as reference.
This is similar to strategy pattern where we determine the running AI agents to determine the root folder or adjust some agents specific stuffs.
I'm still thinking if we could separate these instructions to a separated file outside core-workflow.md
raj-jain-aws
left a comment
raj-jain-aws
left a comment
There was a problem hiding this comment.
Hi @osataken - Nice that the actual rule files are copied and not duplicated. Wondering if we can avoid other content duplications. Also, today many customers ask for customizing AI-DLC. We tell them to drop their rules files in along side our rule files. How would that be done for Kiro Power?
- Simplify POWER.md overview and getting started sections - Add platform detection and file mapping documentation - Remove global installation option (project-local only) - Add kiro-power-file-mapping.md for subfolder-to-flat structure translation - Update core-workflow.md with clearer platform detection logic - Consolidate file loading instructions with priority order - Fix terminology from "Adaptive Intelligent" to "AI-Driven" Development Life Cycle
2 participants
Description of changes:
core-workflow.md
Root README
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.