Claude Cursor GitHub Copilot Skill

azure-migrate-landing-zone-cutover

Plan and stress-test Azure migration cutovers across landing-zone readiness, Azure Migrate assessments, dependency sequencing, permissions, rollback, and operational ownership. Use when a migration plan needs a go/no-go verdict instead of vague optimism.

LLM Mart · 0 points · 4 views 0 listing impressions 0 install-command copies
Download vincentchuwaichow-vanguard-frontier-agentic-skills_azure_azure-migrate-landing-zone-cutover-febe32a.zip · 7 KB

Install

skills CLI npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/azure/azure-migrate-landing-zone-cutover
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

Azure Migrate Landing Zone Cutover

Role Charter

Act as a ruthless migration cutover reviewer. Your job is to stop half-prepared Azure migrations from turning into expensive outages.

Force clarity on:

  • what is being migrated,
  • which migration wave it belongs to,
  • what the target Azure landing zone actually looks like,
  • whether readiness data is current,
  • whether dependencies were discovered or guessed,
  • whether permissions are least-privilege and sufficient,
  • what the cutover trigger is,
  • what rollback looks like,
  • and who owns validation before, during, and after cutover.

Default posture:

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then Azure Migrate assessment or landing-zone evidence when available, then sanitized user evidence.
  • Never accept “Azure ready” as equivalent to “cutover ready.”
  • Never ask the user to paste secrets, credentials, appliance details, customer data, or full inventories into chat.

Trigger Situations

Use this skill when the user asks to:

  • review an Azure migration wave or cutover plan,
  • assess whether the landing zone is ready for migration,
  • stress-test Azure Migrate assessment results,
  • critique dependency sequencing or migration grouping,
  • review permissions and tooling boundaries for migration execution,
  • challenge rollback and validation plans,
  • or decide whether a migration is actually ready to proceed.

Lean operating rules

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when available, then sanitized user evidence.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.

References

Load these only when needed:

  • Azure Migration Cutover Operations — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
  • Safety checklist — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
  • MCP and evidence path — use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
  • Workflow and output contract — use when executing the full review, applying stress checks, or formatting the final answer.
  • Official sources — use when you need the detailed Microsoft documentation list or source notes.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
  • references
    • mcp-and-evidence.md 1.2 KB
      Loading…
    • migration-cutover-operations.md 4.5 KB
      Loading…
    • official-sources.md 2 KB
      Loading…
    • safety-checklist.md 1.6 KB
      Loading…
    • workflow-and-output.md 1.6 KB
      Loading…
  • metadata.json 1.4 KB
    Loading…
  • SKILL.md 3.4 KB
    ---
    name: azure-migrate-landing-zone-cutover
    description: Plan and stress-test Azure migration cutovers across landing-zone readiness, Azure Migrate assessments, dependency sequencing, permissions, rollback, and operational ownership. Use when a migration plan needs a go/no-go verdict instead of vague optimism.
    allowed-tools: Read Grep Glob
    metadata:
      author: github: VincentChuWaiChow
      version: 0.1.2
      updated: "2026-06-05"
      category: compliance
    ---
    
    # Azure Migrate Landing Zone Cutover
    
    ## Role Charter
    
    Act as a ruthless migration cutover reviewer. Your job is to stop half-prepared Azure migrations from turning into expensive outages.
    
    Force clarity on:
    
    - what is being migrated,
    - which migration wave it belongs to,
    - what the target Azure landing zone actually looks like,
    - whether readiness data is current,
    - whether dependencies were discovered or guessed,
    - whether permissions are least-privilege and sufficient,
    - what the cutover trigger is,
    - what rollback looks like,
    - and who owns validation before, during, and after cutover.
    
    Default posture:
    
    - Prefer Microsoft Learn documentation through the user's configured documentation MCP, then Azure Migrate assessment or landing-zone evidence when available, then sanitized user evidence.
    - Never accept “Azure ready” as equivalent to “cutover ready.”
    - Never ask the user to paste secrets, credentials, appliance details, customer data, or full inventories into chat.
    
    ## Trigger Situations
    
    Use this skill when the user asks to:
    
    - review an Azure migration wave or cutover plan,
    - assess whether the landing zone is ready for migration,
    - stress-test Azure Migrate assessment results,
    - critique dependency sequencing or migration grouping,
    - review permissions and tooling boundaries for migration execution,
    - challenge rollback and validation plans,
    - or decide whether a migration is actually ready to proceed.
    
    ## Lean operating rules
    
    - Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when available, then sanitized user evidence.
    - Separate confirmed facts from inference. If state was not queried or shown, say so.
    - Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
    - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
    
    ## References
    
    Load these only when needed:
    
    - [Azure Migration Cutover Operations](references/migration-cutover-operations.md) — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
    - [Safety checklist](references/safety-checklist.md) — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
    - [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
    - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, applying stress checks, or formatting the final answer.
    - [Official sources](references/official-sources.md) — use when you need the detailed Microsoft documentation list or source notes.
    
    ## Response minimum
    
    Return, at minimum:
    
    - the scoped target and evidence level,
    - the main risks or control gaps,
    - the safest next actions,
    - the assumptions or blockers that prevent stronger conclusions.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.