Claude Cursor GitHub Copilot Skill

alibaba-change-impact-advisor

Pre-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.

LLM Mart · 0 points · 3 views 0 listing impressions 0 install-command copies
Download vincentchuwaichow-vanguard-frontier-agentic-skills_alibaba_alibaba-change-impact-advisor-febe32a.zip · 4 KB

Install

skills CLI npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/alibaba/alibaba-change-impact-advisor
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
Git git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Alibaba Cloud Change Impact Advisor

Purpose

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.

When to use

Use this skill for:

  • pre-change impact analysis: Resource Directory OU scope, RAM policy cascades, CEN route propagation
  • VPC peering topology assessment and CEN blast radius mapping
  • SLB backend pool change risk and blue/green swap sequencing
  • RDS connection pool disruption analysis and connection drain planning
  • safe change sequencing and rollback plan construction
  • dual-approval gate requirements for root-level Resource Directory changes

Lean operating rules

  • Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
  • Separate confirmed facts from inference. If a dependency was not verified, say so.
  • Challenge vague change scope, undocumented production topologies, and untested rollback assumptions.
  • Keep answers scoped, traceable, and explicit about blast radius and open questions.
  • Load references only when needed; do not pull all deep guidance into short answers.

Key blast radius guidance

  • Resource Directory OUs: An OU-level policy change cascades to all member accounts under that OU — enumerate all affected accounts before proceeding.
  • 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.
  • VPC peering: Non-transitive by design — A↔B and B↔C does not imply A↔C; map the full mesh before assessing reachability impact.
  • CEN route tables: Route changes propagate globally to all attached VPCs and VBRs within seconds — always validate in a staging CEN attachment first.
  • 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.
  • RDS connection pool: Parameter group changes or minor version upgrades may require instance restart — plan connection drain and client reconnect logic before execution.
  • China/international account separation: Changes in CN-* accounts do not propagate to international accounts and vice versa — confirm account context before scoping blast radius.

References

Load these only when needed:

  • Workflow and output contract — use when executing the full change impact analysis or formatting the final assessment output.
  • Official sources — use when grounding Alibaba Cloud service behavior or dependency behavior claims.

Response minimum

Return, at minimum:

  • the change description and target resources,
  • the Resource Directory OU scope and affected accounts,
  • the RAM policy cascade and cross-account STS impact,
  • the VPC/CEN network topology impact,
  • the safe change sequencing recommendation with rollback plan,
  • the open questions that must be resolved before execution.
Files (vanguard-frontier-agentic)
  • references
    • official-sources.md 1022 B
      Loading…
    • workflow-and-output.md 2.9 KB
      Loading…
  • metadata.json 1.3 KB
    Loading…
  • SKILL.md 3.6 KB
    ---
    name: alibaba-change-impact-advisor
    description: Pre-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.
    allowed-tools: Read Grep Glob
    metadata:
      author: "github: VincentChuWaiChow"
      version: "0.1.0"
      updated: "2026-05-09"
      category: platform
    ---
    
    # Alibaba Cloud Change Impact Advisor
    
    ## Purpose
    
    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.
    
    ## When to use
    
    Use this skill for:
    
    - pre-change impact analysis: Resource Directory OU scope, RAM policy cascades, CEN route propagation
    - VPC peering topology assessment and CEN blast radius mapping
    - SLB backend pool change risk and blue/green swap sequencing
    - RDS connection pool disruption analysis and connection drain planning
    - safe change sequencing and rollback plan construction
    - dual-approval gate requirements for root-level Resource Directory changes
    
    ## Lean operating rules
    
    - Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
    - Separate confirmed facts from inference. If a dependency was not verified, say so.
    - Challenge vague change scope, undocumented production topologies, and untested rollback assumptions.
    - Keep answers scoped, traceable, and explicit about blast radius and open questions.
    - Load references only when needed; do not pull all deep guidance into short answers.
    
    ## Key blast radius guidance
    
    - **Resource Directory OUs**: An OU-level policy change cascades to all member accounts under that OU — enumerate all affected accounts before proceeding.
    - **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.
    - **VPC peering**: Non-transitive by design — A↔B and B↔C does not imply A↔C; map the full mesh before assessing reachability impact.
    - **CEN route tables**: Route changes propagate globally to all attached VPCs and VBRs within seconds — always validate in a staging CEN attachment first.
    - **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.
    - **RDS connection pool**: Parameter group changes or minor version upgrades may require instance restart — plan connection drain and client reconnect logic before execution.
    - **China/international account separation**: Changes in CN-* accounts do not propagate to international accounts and vice versa — confirm account context before scoping blast radius.
    
    ## References
    
    Load these only when needed:
    
    - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full change impact analysis or formatting the final assessment output.
    - [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud service behavior or dependency behavior claims.
    
    ## Response minimum
    
    Return, at minimum:
    
    - the change description and target resources,
    - the Resource Directory OU scope and affected accounts,
    - the RAM policy cascade and cross-account STS impact,
    - the VPC/CEN network topology impact,
    - the safe change sequencing recommendation with rollback plan,
    - the open questions that must be resolved before execution.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.