What problem does it solve? Turning a working conversation into a well-formed tracker ticket is tedious and error-prone: descriptions lose context, metadata IDs require manual lookup, and tickets often narrate session progress instead of describing the problem. This Skill drafts a developer-ready ticket from the current conversation and delegates tracker creation to a subagent. ## Core Features & Use Cases - Context-driven drafting: Synthesizes the conversation into a ticket with title, context, problem, desired outcome, acceptance criteria, and technical notes written in a Product Engineer voice. - Status from real work state: Files the ticket in the backlog when nothing has started, or in progress and assigned when code already changed, keeping the board honest. - Subagent delegation: A single subagent resolves team, status, priority, and assignee identifiers against the live tracker and creates the ticket, keeping noisy API lookups out of the main context. - Use Case: After a debugging session reveals a missing retry mechanism, ask for a ticket and get a clean description file plus a created tracker issue with correct team, status, and assignee. ## Quick Start Ask the assistant to create a ticket from this conversation for the payment webhook retry problem under the Platform team.
