What problem does it solve? Business rules are often described inconsistently across stakeholders, and BDD scenarios get written from assumptions or implementation details rather than verified facts. This Skill enforces a shared discipline for writing BDD only from grounded inputs—user statements, explicit documents, and decisions confirmed through structured dialogue—so every scenario is traceable to a source. ## Core Features & Use Cases - Grounded Input Discipline: Distinguishes confirmed facts, hypotheses, and unresolved questions, and forbids filling gaps with general knowledge or plausible examples. - Business-Language BDD: Writes scenarios in ubiquitous language with explicit Given/When/Then, mandatory NOTE blocks (Rule/Source/Reason) for failure cases, and a JSON condition matrix validated before content is saved. - Formulation Readiness & QA Falsification: Judges whether existing understanding is ready for formulation, then applies QA perspectives (boundaries, concurrency, permissions, time, failure guarantees) to refute claims. - Use Case: When a discovery or formulation entry point needs to document a reservation cancellation rule, this Skill ensures each scenario lists all preconditions, ties rejections to a specific business rule, and routes open questions through the grill contract before writing via write-doc. ## Quick Start Apply the write-bdd discipline to turn the confirmed reservation cancellation decisions into BDD scenarios with a condition matrix and failure notes.
