What problem does it solve? Teams often jump into code changes without a shared, verified understanding of what the business should actually do, leading to wrong assumptions, invented behavior, and rework. This Skill structures the discovery of business intent — classifying the task mode, framing expected vs observed behavior, asking only blocking questions, and producing a confirmed business-context artifact that downstream architecture, planning, and review stages rely on. ## Core Features & Use Cases - Mode classification: Distinguishes Mode A (existing behavior — bugs, enhancements, refactors) from Mode B (new features) and applies the right discovery procedure for each. - Evidence-first verification: Every claim about current behavior is verified against the code and cited as path:line, or marked UNVERIFIED — no assumptions allowed. - Blocking-question discipline: Separates questions that block business definition from non-blocking ones, and forbids technical questions at this stage. - Confirmed artifact: Writes a business-context.md file with confidence labels (Provided / Confirmed / Inferred / Unknown), acceptance criteria, and a human confirmation gate. - Use Case: A developer reports "discount approval flow is broken." The Skill frames the user, flow, expected vs observed behavior, asks what should happen after rejection, and produces a confirmed business context the architect can design against. ## Quick Start Ask the agent to establish the business context for your task, for example: "Establish the business context for the quote discount approval bug before we design a fix."
