Skip to content

docs(migrate): sync plugin READMEs with Heroku skill and ai-to-aws#84

Open
herosjourney wants to merge 2 commits into
awslabs:mainfrom
herosjourney:docs/readme-sync-heroku-ai
Open

docs(migrate): sync plugin READMEs with Heroku skill and ai-to-aws#84
herosjourney wants to merge 2 commits into
awslabs:mainfrom
herosjourney:docs/readme-sync-heroku-ai

Conversation

@herosjourney

Copy link
Copy Markdown
Contributor

Summary

Problem

The migration-to-aws/README.md still described a GCP-only plugin with no mention of Heroku or the ai-to-aws execution companion. Users installing the plugin wouldn't know it supports Heroku migrations or that an execution layer exists.

The ai-to-aws/README.md used @startups-for-aws as the install tag while the parent migrate/README.md uses @startups — one copy-paste away from a failed install.

Changes

migrate/plugins/migration-to-aws/README.md:

  • Add Heroku as a supported source throughout (intro, detection tables, triggers, requirements)
  • Add ai-to-aws to the Plugins table with relationship description
  • Add heroku-to-aws agent skill trigger table
  • Update Workflow section to be source-agnostic
  • Add Heroku-specific and ai-to-aws-specific requirements
  • Update Development section to reference both skill directories

migrate/plugins/ai-to-aws/README.md:

  • Fix all 3 install tag references from @startups-for-aws to @startups

Type of Change

  • New plugin/power/tool
  • Bug fix
  • Enhancement to existing content
  • Documentation update
  • Guardrail/CI update

Team Folder

  • migrate/

Checklist

  • I have read the CONTRIBUTING.md guidelines
  • My changes do not include hardcoded secrets, credentials, or internal-only content
  • I have updated documentation if needed
  • My changes are scoped to my team's folder only

…ugin

- migration-to-aws/README.md: add Heroku detection table, heroku-to-aws
  triggers, ai-to-aws plugin reference, update workflow to be
  source-agnostic, add Heroku-specific requirements
- ai-to-aws/README.md: fix install tag from @startups-for-aws to
  @startups to match canonical format in migrate/README.md
@herosjourney herosjourney requested a review from a team as a code owner June 26, 2026 05:36
The heroku-to-aws skill supports Dynos → EKS (Q12c in Clarify, full
generate-eks.md generation path), but the parent migrate/README.md
only documented Fargate. Update:

- Supported sources bullet: Dynos (→ Fargate or EKS)
- How to Use examples: add "Migrate from Heroku to EKS"
- Heroku → AWS table: Fargate or EKS with user-chooses note
- Agent Skill Triggers: add "migrate dynos to EKS"
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