What problem does it solve? Raw requirements arrive as unstructured Jira tickets, emails, meeting notes, or documents, and teams often start drafting user stories before scope, NFRs, and open questions are settled. This Skill structures that intake step into a typed Scope Sheet contract with an explicit human approval gate before any stories are written. ## Core Features & Use Cases - Scope Sheet Generation: Produces a typed contract with business goal, explicit in-scope and out-of-scope lists, quantified NFRs, assumptions, and risk flags wrapped in a shared pipeline envelope. - Open Question Management: Converts every ambiguity into a numbered open question (OQ-n) with an assigned owner (BA, PM, or SME) instead of burying it as a silent assumption. - Readiness Gating: Emits a ready-for-stories or needs-clarification state and stops at the G1 gate where a BA or PM confirms scope before drafting begins. - Use Case: A product team receives a vague e-commerce MVP spec. Run intake to get a Scope Sheet that flags the unquantified "fast" requirement as an open question, lists deferred Phase-2 items as out-of-scope, and marks the requirement ready for story drafting. ## Quick Start Run BA intake on this requirement and produce the Scope Sheet for the pipeline.
