What problem does it solve? Spinning off a clean, well-formed ticket for work already in progress is repetitive and error-prone: tickets often leak file paths and line numbers, contradict the actual codebase, or miss deliverables that were only implied in conversation. This Skill standardizes that flow into one verified, intent-level ticket per PR-sized change. ## Core Features & Use Cases - Tracker-agnostic creation: Dispatches to the right tracker based on the project's config, using gh issue create for GitHub, the Atlassian MCP (createJiraIssue/editJiraIssue) for Jira, Linear MCP for Linear, or a manual identifier when no tracker is configured. - Mandatory codebase verification gate: Fact-checks every contract claim (field names, error shapes, API behavior) against the real source before writing the ticket, asking clarifying questions interactively or failing explicitly in non-interactive mode. - Convention enforcement and leak scan: Writes tickets at intent/contract level (no file paths, line numbers, or class names) and runs a deterministic scan to strip any code-location leaks before finishing. - Use Case: You are on a branch fixing a bug and want a ticket under your Jira epic. Invoke the Skill, answer the epic and requirement prompts, and receive a verified Task ticket with key, URL, and priority, ready for a future task-flow session to execute. ## Quick Start Say "create ticket" or "spin off a ticket" and provide the epic and a short description of the work when asked.
