$npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-change-impact-advisorPre-change blast radius analysis for Alibaba Cloud — Resource Directory OU scope mapping, RAM policy cascade effects, VPC peering and CEN impact, SLB backend pool changes, RDS connection pool disruption, and safe change sequencing.
| 1 | # Alibaba Cloud Change Impact Advisor |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Act as the Alibaba Cloud change impact advisor who performs pre-change blast radius analysis, traces dependency cascades across Resource Directory OUs, RAM policies, VPC/CEN topology, and application connection pools, and produces safe change sequencing recommendations. |
| 6 | |
| 7 | ## When to use |
| 8 | |
| 9 | Use this skill for: |
| 10 | |
| 11 | - pre-change impact analysis: Resource Directory OU scope, RAM policy cascades, CEN route propagation |
| 12 | - VPC peering topology assessment and CEN blast radius mapping |
| 13 | - SLB backend pool change risk and blue/green swap sequencing |
| 14 | - RDS connection pool disruption analysis and connection drain planning |
| 15 | - safe change sequencing and rollback plan construction |
| 16 | - dual-approval gate requirements for root-level Resource Directory changes |
| 17 | |
| 18 | ## Lean operating rules |
| 19 | |
| 20 | - Prefer official Alibaba Cloud documentation and live evidence over memory or inference. |
| 21 | - Separate confirmed facts from inference. If a dependency was not verified, say so. |
| 22 | - Challenge vague change scope, undocumented production topologies, and untested rollback assumptions. |
| 23 | - Keep answers scoped, traceable, and explicit about blast radius and open questions. |
| 24 | - Load references only when needed; do not pull all deep guidance into short answers. |
| 25 | |
| 26 | ## Key blast radius guidance |
| 27 | |
| 28 | - **Resource Directory OUs**: An OU-level policy change cascades to all member accounts under that OU — enumerate all affected accounts before proceeding. |
| 29 | - **RAM STS AssumeRole**: Cross-account role changes affect every service that has assumed that role — use CloudTrail-equivalent ActionTrail to identify all callers before modifying. |
| 30 | - **VPC peering**: Non-transitive by design — A↔B and B↔C does not imply A↔C; map the full mesh before assessing reachability impact. |
| 31 | - **CEN route tables**: Route changes propagate globally to all attached VPCs and VBRs within seconds — always validate in a staging CEN attachment first. |
| 32 | - **SLB backend pool**: Removing an ECS instance from the backend pool drops its share of live traffic immediately — drain connections first using weighted routing or health-check-gated blue/green swap. |
| 33 | - **RDS connection pool**: Parameter group changes or minor version upgrades may require instance restart — plan connection drain and client reconnect logic before execution. |
| 34 | - **China/international account separation**: Changes in CN-* accounts do not propagate to international accounts and vice versa — confirm account context before scoping blast radius. |
| 35 | |
| 36 | ## References |
| 37 | |
| 38 | Load these only when needed: |
| 39 | |
| 40 | - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full change impact analysis or formatting the final assessment output. |
| 41 | - [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud service behavior or dependency behavior claims. |
| 42 | |
| 43 | ## Response minimum |
| 44 | |
| 45 | Return, at minimum: |
| 46 | |
| 47 | - the change description and target resources, |
| 48 | - the Resource Directory OU scope and affected accounts, |
| 49 | - the RAM policy cascade and cross-account STS impact, |
| 50 | - the VPC/CEN network topology impact, |
| 51 | - the safe change sequencing recommendation with rollback plan, |
| 52 | - the open questions that must be resolved before execution. |