gh-ticketlisted

# GitHub Ticket (Create or Update) ## Why This Skill Exists **The moment you decide to create a ticket, you have MAXIMUM CONTEXT.** - You just investigated the problem - You understand the codebase state - You know the requirements - You have the error messages fresh - You understand the dependencies **If you don't capture this NOW, it's lost forever.** The implementer (even if it's you later) will have to re-discover everything. ## The Cost of Vague Tickets | Vague Ticket | Cost | |--------------|------| | "Fix auth bug" | Implementer spends 2 hours finding which bug | | "Add user settings" | 5 back-and-forth clarifications | | "Improve performance" | Implementation doesn't match intent | | "Handle edge case" | Which edge case? What behavior? | **Every minute spent writing a good ticket saves 10 minutes of implementation confusion.** --- ## When to Use This Skill - **Creating** a new GitHub issue - **Updating** an existing issue with new context/requirements - **Expanding** a vague issue into a comprehensive spec - **Adding** implementation details discovered during investigation --- ## Ticket Process (Create or Update) ### Phase 1: Context Capture (DO THIS FIRST) Before writing anything, gather ALL available context: #### Step 1: Dump Current Context Ask yourself and document: ```markdown ## Context Dump (will be refined) ### What triggered this? - [User request? Bug report? Code review finding? Your own observation?] ### What do I know right now? - [Ever