What problem does it solve? Writing test plans for Kubernetes controllers often produces shallow happy-path checklists that miss negative cases, boundary conditions, and topology variations where real defects hide. This Skill systematically enumerates a complete, falsifiable test scenario matrix so coverage gaps are declared rather than silently assumed. ## Core Features & Use Cases - Paired positive and negative enumeration: Every positive behavior mechanically derives negatives (absent preconditions, invalid inputs, RBAC denials, control-plane 4xx/5xx/timeout, concurrency conflicts, mid-operation interruption) so no behavior group ships without failure cases. - Coverage axis expansion: Scenarios are expanded across cluster topology (single-node, three-node, 5+), namespace scope, cluster count, failure domains, object scale, lifecycle timing, and version skew, with an auditable axis coverage table. - Honest gap reporting: Untested axis combinations are listed in a gap table with reasons instead of being silently dropped. - Use Case: When designing a new volume migration feature in the simplyblock operator, invoke this Skill to produce the numbered U-/I-/E-/M- scenario rows for the design document's test plan, including single-node no-target cases and operator-restart idempotency checks. ## Quick Start Ask the AI to enumerate the test scenario matrix for a specific feature, CRD, or controller, for example by requesting test scenarios for the storage node drain reconciler.
