What problem does it solve? Business rules are often described inconsistently across stakeholders, with boundary conditions and permissions left undefined. This Skill turns fragmented business knowledge into a single authoritative domain-rule document containing representative BDD scenarios, so business people and developers share the same understanding before implementation or QA begins. ## Core Features & Use Cases - Structured discovery workflow: Follows a playbook of settle, ground, explore, scope, record-behavior, validate, and document steps, using the grill plugin to ask only skeleton-defining questions. - Business vs. implementation boundary: Separates durable business rules from UI, API, data model, and operational concerns, recording excluded items with reasons. - Deterministic validation scripts: Checks the BDD condition matrix structure and verifies that the commands/queries table matches the actor-permission table before saving. - Use Case: Given only the phrase "reservations can be cancelled," the Skill explores who can cancel, in which states, under what conditions acceptance or rejection occurs, and saves a domain-rule document with representative Given/When/Then scenarios. ## Quick Start Ask the agent to discover the core domain rules for reservation cancellation from the existing glossary and requirements documents and produce a domain-rule document with representative BDD scenarios.
