pantheon-ai/cfn-behavior-validator
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
task.mdevals/scenario-5/
Automate ECS Task Definition Memory Change Validation
Problem Description
Your DevOps team regularly needs to validate CloudFormation update behaviors for various resource property changes. To make this process more efficient, they want to leverage automation tools and scripts that can stream events in real-time during deployments and compare resource properties before and after changes.
For an upcoming test of ECS task definition memory limit changes (from 512 to 1024), you need to set up an automated monitoring and comparison workflow.
Output Specification
Create a file automation-workflow.md that documents:
- Real-time Monitoring Setup: How to monitor CloudFormation events as they happen during the deployment (not just querying after the fact)
- Resource Comparison Strategy: How to capture and compare resource properties before and after the deployment
- Tool Usage: What scripts or tools would be most useful for this automation
- Workflow Steps: The complete sequence of automated steps from initial deployment through final comparison
The document should demonstrate knowledge of available helper tools and automation approaches for validation testing, even if the actual scripts don't exist in your environment.
Also create a simple bash script monitor-deployment.sh that shows the general approach to monitoring a deployment in progress (use comments liberally to explain the approach even if you don't have access to actual helper scripts).