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-for…