What problem does it solve? Software correctness often depends on engineers remembering edge cases under pressure. This Skill pushes correctness into the structure of the system itself—boundaries, invariants, resource limits, idempotency, and rollout shape—so a tired engineer can make a correct change without holding everything in their head. ## Core Features & Use Cases - Structural review framework: Provides a default output template covering boundaries and invariants, time and resource safety, failure and observability, and change lifecycle, with explicit must-fix versus can-defer decisions. - Blast-radius tiebreaker: Decides between competing principles based on whether input is caller-, attacker-, dependency-, or environment-controlled and how wide the blast radius is. - Phase-specific subskills: Routes work to focused subskills for triage, planning, implementing, integrating, reviewing, verifying, operating, investigating, retrospectives, and retirement. - Use Case: When reviewing an urgent checkout double-charge fix, the Skill produces a structured analysis covering idempotency keys, atomic state transitions, ambiguous timeout handling, and red-before/green-after verification against the running system. ## Quick Start Ask the agent to review your design, PR, or incident plan using the structural-correctness skill and to separate must-fix items from can-defer items.
