Creates test stacks, analyzes CloudFormation events, and compares actual vs documented update behavior to validate whether resource property changes trigger replacement or in-place updates. Use when: a user wants to test if a CFN property change causes resource replacement; when investigating stack update behavior or "Update requires" documentation accuracy; when validating whether a workaround (e.g. hash-based logical IDs) is actually necessary; when questioning UpdateRequiresReplacement behavior for immutable properties; when empirical evidence is needed before an architectural decision involving CDK or CloudFormation stack updates.
Does it follow best practices?
Evaluation — 100%
↑ 1.12xAgent success when using this tile
Validation for skill structure
Your team needs to understand whether changing a Lambda function's memory configuration from 128MB to 512MB triggers a function replacement or an in-place update. This is critical because the function maintains state through environment variables that reference other resources, and a replacement could cause temporary service disruption.
Before testing this in your integration environment, you need to design a proper test infrastructure that isolates this specific change and allows for clear observation of CloudFormation's behavior.
Create a TypeScript CDK stack file named memory-test-stack.ts that:
Also create a file test-execution-plan.md that describes:
The stack should be production-quality CDK code but focused solely on testing this one behavior.