Skip to content

migration-to-aws: flat-steering port with scripts shipped directly - #182

Open
ayn-builds wants to merge 1 commit into
kirodotdev:mainfrom
ayn-builds:ayn/migration-to-aws-flat-scripts-upstream
Open

migration-to-aws: flat-steering port with scripts shipped directly#182
ayn-builds wants to merge 1 commit into
kirodotdev:mainfrom
ayn-builds:ayn/migration-to-aws-flat-scripts-upstream

Conversation

@ayn-builds

Copy link
Copy Markdown

Reworks the migration-to-aws flattening of the upstream awslabs plugin (awslabs/startups/migrate/plugins/migration-to-aws, Apache-2.0) so the plugin's deterministic scripts ship as real executables rather than de-scripted prose.

  • Ships 11 PEP 723 .py scripts flat in steering/, invoked as uv run steering/<name>.py (agent-advisor scoring/build-diagram, the llm validators, the tf policy checker). No servers/ dir.
  • Adds the agent-advisor and llm-to-bedrock engines alongside gcp-to-aws and heroku-to-aws, plus shared tf-best-practices
  • Defines $STEERING/$SCRIPTS/$HELPERS/<scriptsDir>/$GCP_BASE in POWER.md so they resolve to the one flat directory, and the plugin's injected "Scripts directory" line is no longer load-bearing
  • INTERPRETER.md _exec dispatches to Kiro's generic general-task-execution sub-agent, so context isolation survives the loss of a power-level agent registry
  • Generated by tooling/flatten_plugin_to_power.py, so re-syncing is a re-run rather than a manual merge

Additive over the current power: all 67 existing migration-to-aws/ files are retained, nothing is deleted, and no other power is touched.

Reworks the flattening of the upstream awslabs plugin
(awslabs/startups/migrate/plugins/migration-to-aws, Apache-2.0) so the
plugin's deterministic scripts ship as real executables rather than being
de-scripted into prose.

- Ships 11 PEP 723 .py scripts flat in steering/, run via
  `uv run steering/<name>.py` (agent-advisor scoring/build-diagram, the
  llm validators, the tf policy checker). No servers/ MCP dir.
- Adds the agent-advisor and llm-to-bedrock engines alongside gcp-to-aws
  and heroku-to-aws, plus shared tf-best-practices.
- POWER.md defines $STEERING/$SCRIPTS/$HELPERS/<scriptsDir>/$GCP_BASE to
  resolve to the one flat directory, so the plugin's injected "Scripts
  directory" line is no longer load-bearing.
- INTERPRETER.md _exec dispatches to Kiro's generic general-task-execution
  sub-agent, preserving context isolation without a power-level agent
  registry.
- Generated by tooling/flatten_plugin_to_power.py, so a re-sync is a
  re-run rather than a manual merge.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant