What problem does it solve? Vague or incomplete requirements cause rework and misaligned implementations. This Skill runs a structured Analysis & Discovery phase that challenges assumptions, asks clarifying questions, and produces an actionable requirements document before any design or coding begins. ## Core Features & Use Cases - Domain Detection: Automatically detects whether the project is software, business, or personal by scanning for markers like package.json, business-plan.md, or goals.md, and adapts its questions accordingly. - Structured Requirements Output: Generates a requirements.md (or business-brief.md / personal-brief.md) with objectives, stakeholders, functional requirements with acceptance criteria, non-functional requirements, constraints, risks, and explicit out-of-scope items. - Handoff Digest & Traceability: Optionally writes a handoff digest for the next role and integrates with Linear to link requirements to issues. - Use Case: Before building a new feature, run this Skill to interview yourself on objectives, users, constraints, and success metrics, then receive a requirements document ready to hand to an architect or product refiner. ## Quick Start Ask the Scope Clarifier to gather requirements for your new feature and produce a requirements document with acceptance criteria.
