What problem does it solve? Existing domain-rule documents often miss boundary conditions, rejection criteria, and actor permissions, leaving business rules ambiguous. This Skill challenges an existing domain-rule document with QA-perspective counterexamples and writes confirmed findings back into the same file, deepening shared business understanding without creating new documents. ## Core Features & Use Cases - QA-driven refutation: Applies structured questioning (via the grill plugin) to challenge existing business rules with boundary values, concurrency, and permission edge cases. - BDD scenario validation: Validates Gherkin drafts against condition matrices using scripts/scenario.py, and checks actor coverage consistency between command/query tables and permission tables. - In-place document update: Guards that the output path matches the existing source document (scripts/update-guard.py) and writes the revised domain-rule back via the write-doc plugin. - Use Case: Given an existing reservation-cancellation domain-rule document, challenge it with scenarios like cancellation exactly at the deadline and double cancellation, then update the same document with confirmed boundary rules and open questions. ## Quick Start Challenge my existing reservation-cancellation domain-rule document with boundary scenarios like the exact deadline and duplicate cancellation, and update the same file with the confirmed findings.
