What problem does it solve? Development workflows need requirement content from many places — a quick prompt, an existing ticket, or a Notion doc — and each source arrives in a different shape. This Skill normalizes all of them into one consistent structured input so downstream ticket creation works the same regardless of origin. ## Core Features & Use Cases - Source Dispatch: Routes a (source, ref) pair to the correct handler: prompt for raw text, existing-ticket for a ticket ID, or notion-page for a Notion URL or page ID. - Normalized Output: Every source returns the same shape — title, body (with Requirements, Acceptance Criteria, Context, Open Questions sections), sourceRef, and a confidence rating. - Confidence Calibration: Assigns high/medium/low confidence based on how complete the source content is, which the ticket interviewer uses to decide how deeply to question the user. - Use Case: A user runs /notion-dev:create-task pointing at a Notion design doc; this Skill fetches the page via the Notion MCP, converts blocks to markdown, and hands structured input to the ticket-writing step. ## Quick Start Ask the assistant to ingest requirements from a Notion page URL using the input-source skill and return the structured ticket draft.
