What problem does it solve? Turning a vague feature or bug request into a well-scoped GitHub issue requires clarifying requirements, capturing decisions, and wiring up project tracking. This Skill structures that ticket-definition stage so issues carry a clear contract before any technical research begins. ## Core Features & Use Cases - Scoped requirement gathering: Asks a small batch of decision-bearing questions about interface, identity, invalid inputs, persistence, and verification, then captures a concise contract with acceptance examples. - GitHub issue lifecycle: Creates new issues with gh issue create, or updates an existing issue only after explicit user confirmation, preserving prior content and status. - Project and Orca tracking: Adds issues to the configured project, sets Backlog status, links Orca via track.py link-orca, and records verified contract checkpoints with handoff.py. - Use Case: A user says "/ticket add rate limiting to the API". The Skill asks targeted scoping questions, drafts the issue body, creates the GitHub issue assigned to the user, attaches it to the configured project and Orca, and records a v2 contract for the research stage. ## Quick Start Ask the assistant to create a ticket for the feature or bug you have in mind, for example by saying "/ticket add pagination to the users endpoint".
