What problem does it solve? Draft tickets often arrive with vague goals, missing acceptance criteria, or unexamined edge cases, causing engineers to build the wrong thing. This Skill runs a calibrated interview that closes every requirement gap before the ticket is written to the ticket system. ## Core Features & Use Cases - Confidence-Adaptive Depth: Adjusts interview depth based on a high/medium/low confidence hint from the input source, skipping phases when the draft is already complete. - Clarity Audit: Validates goal, scope, acceptance criteria, edge cases, dependencies, and data shape before finishing, with a downshift rule when structural gaps appear. - Structured Output: Returns a markdown ticket body with Requirements, Acceptance Criteria, Context, Open Questions, and Source headings, plus an optional type classification. - Use Case: During /notion-dev:create-task Phase 2, a rough one-line feature idea is turned into a ticket two engineers could independently implement to the same result. ## Quick Start Ask the assistant to interview you about a draft ticket so its goal, scope, and acceptance criteria are fully clarified before it is written to the ticket system.
