clarity--ticket-writer

To turn vague stakeholder requests into actionable engineering tickets, you provide the raw request input to trigger a triage process that asks targeted clarifying questions and outputs a structured ticket with acceptance criteria, complexity tier, and target files.

Writing acceptance criteria for ambiguous product management tasks requires capturing stakeholder decisions through targeted questions, then structuring those decisions into formal ticket fields with explicit complexity tiers and design notes for engineering execution.

You can refine feature requests to include target files and complexity tiers by processing the initial request through a structured ticket generation workflow that evaluates scope and outputs these specific engineering fields.

This ticket writing approach works for reviewing incoming ad-hoc requirements by triaging the ambiguous input, identifying scope and risk through targeted questions, and producing a production-ready ticket with necessary references.

A production-ready work ticket should include a structured title, description, acceptance criteria, complexity tier, target files, design notes, and optional references or assets to guide engineering work confidently.

Stakeholder requests lead to misaligned expectations during ticket writing because vagueness in the initial input creates ambiguous work items, which structured ticket generation with formal acceptance criteria resolves.