What problem does it solve? When a feature request or change has unclear goals, scope, or success criteria, teams risk building the wrong thing or arguing about done-ness later. This Skill turns ambiguous intent into a compact acceptance contract that any developer, agent, or reviewer can evaluate without the original conversation. ## Core Features & Use Cases - Outcome Clarification: Extracts the user, situation, problem, desired outcome, scope, and exclusions from requests and existing product artifacts, asking only questions that require human judgment. - Acceptance Contract Authoring: Produces Given/When/Then scenarios with stable criterion IDs, evidence requirements (automated test, demonstration, measurement, or human review), and identified decision owners. - Verification Discipline: Reports criteria as passed, failed, blocked, or awaiting human review, keeping required evidence distinct from collected evidence and preventing premature done claims. - Use Case: Before implementing a status-filtering feature, use this Skill to record the observable scenarios, boundary cases, and evidence plan in the owning issue so implementation and review share one definition of success. ## Quick Start Ask the agent to define the outcome and acceptance criteria for your feature request before any implementation begins.
