cloudformation-cross-stack-export-prison

Diagnose CloudFormation cross-stack export dependencies blocking stack updates.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/cajias/claude-skills --skill cloudformation-cross-stack-export-prison
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloudformation-cross-stack-export-prison
Source: https://github.com/cajias/claude-skills/tree/main/skills/cloudformation-cross-stack-export-prison
Command: npx skills add https://github.com/cajias/claude-skills --skill cloudformation-cross-stack-export-prison

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you recover from CloudFormation and CDK deployment deadlocks caused by cross-stack export dependencies, especially when one stack cannot update or delete an export that other stacks still import.

Core Features & Use Cases

  • Diagnose export dependency deadlocks: Identify when Fn::ImportValue, CDK auto-generated exports, or shared stack outputs are blocking infrastructure changes.
  • Choose a safe migration path: Apply strategies such as stack prefix isolation, SSM Parameter Store replacement, direct property wiring, or manual teardown and recreation.
  • Prevent repeat failures: Validate exports and imports before deployment, check diffs for export changes, and plan around shared resource reconstruction.
  • Use case: A Cognito or shared foundation stack must be changed, but multiple downstream stacks still depend on its exported values, preventing an in-place update.

Quick Start

Ask Claude to analyze your CloudFormation or CDK stack dependency deadlock and recommend the safest migration plan for replacing the blocked export without breaking dependent stacks.

Frequently Asked Questions about cloudformation-cross-stack-export-prison

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my CloudFormation stack update fail when other stacks import its exports?

CloudFormation stack updates fail because downstream stacks still reference the exported values via Fn::ImportValue, creating a deployment deadlock that requires analyzing import chains to resolve safely.

How do I replace CloudFormation cross-stack exports without breaking dependent stacks?

To replace cross-stack exports safely, analyze importing stacks and apply migration patterns like SSM Parameter Store replacement, direct property wiring, or stack prefix isolation to decouple dependencies before deployment.

Can I use SSM Parameter Store instead of CloudFormation exports to share resources across stacks?

Yes, SSM Parameter Store can replace CloudFormation exports to share resources across stacks, allowing independent stack updates by removing the strict coupling that Fn::ImportValue creates between exporting and importing stacks.

What is the best way to resolve CDK cross-stack export dependency deadlocks during infrastructure refactoring?

The best way to resolve CDK cross-stack export deadlocks is to diagnose auto-generated exports and importing stacks, then apply controlled stack recreation or shared resource migration patterns to safely decouple the infrastructure.

How do I diagnose circular import chains blocking my CDK stack deployments?

Diagnose circular import chains by analyzing export names and identifying which importing stacks reference them, determining if CDK auto-generated exports or shared stack outputs are preventing infrastructure changes.