Setting the file. One moment.
Subchapter 23.40
references/phases/migration-plan/migration-plan-gcp-constraints.mdMarkdown4 KBView on GitHub
Loaded by migration-plan.md Step 2.5. These constraints mirror gcp-to-aws’s SKILL.md
and govern every phase that migration-plan.md executes inline. Apply them exactly as if
gcp-to-aws’s own state machine were running.
google_bigquery_* in IaC or
billing rows), STOP the migration and surface the specialist advisory before Design. Do
not recommend a specific AWS analytics service; direct the user to their AWS account team.Each phase should load no more than ~800 lines of instructions. Load conditional reference
files (design-refs/, sub-files) ONLY when their trigger condition is met — do not
speculatively load all sub-files.
Always-load files in Generate (do not skip even when context is tight):
generate-artifacts-docs.md — produces MIGRATION_GUIDE.md + README.md (mandatory)generate-artifacts-report.md — produces migration-report.html and opens it in the
browser. This is the final step of Generate and must NOT be skipped. It runs
open "$MIGRATION_DIR/migration-report.html" (macOS) or
xdg-open "$MIGRATION_DIR/migration-report.html" (Linux) after writing the file.Conditional files (load ONLY when condition is true):
| File | Condition |
|---|---|
design-refs/ai-gemini-to-bedrock.md | ai-workload-profile.json exists AND summary.ai_source = "gemini" or "both" |
vendored/ai/ai-openai-to-bedrock.md | ai-workload-profile.json exists AND summary.ai_source = "openai" or "both" |
vendored/ai/ai-anthropic-to-bedrock.md | ai-workload-profile.json exists AND summary.ai_source = "anthropic" |
design-refs/ai.md | ai-workload-profile.json exists AND summary.ai_source = "other" |
vendored/ai/design-ref-harness.md | agentic_profile.is_agentic == true AND migration_approach == "harness" |
vendored/ai/design-ref-agentic-to-agentcore.md | agentic_profile.is_agentic == true AND migration_approach == "strands" |
shared/retarget-gotchas.md | agentic_profile.is_agentic == true AND migration_approach == "retarget" |
All paths above are relative to $GCP_BASE/references/ (defined in migration-plan.md).
gcp-to-aws’s discover.md and estimate.md each offer a feedback prompt after their
HANDOFF_OK. Because this execution runs inside agent-advisor’s session, automatically
choose “skip feedback” (option B) at both sidebars and continue to the next phase. Do
NOT load $GCP_BASE/references/phases/feedback/feedback.md.
When both gcp-resource-inventory.json AND ai-workload-profile.json exist in
$MIGRATION_DIR, the combined design refs approach the ~800 line budget. Present the
user with the option to run infrastructure and AI workloads as two separate passes (as
specified in gcp-to-aws’s SKILL.md hybrid stack warning), then continue based on their
answer.