slash command to start working on new tickets

ticket.md

allowed-tools	description
Bash(git log:*), Bash(git config:*), Bash(git diff:*), Bash(git branch:*), Read, Glob, Bash(git rev-parse:*), Bash(gh)	Research a ticket and create an execution plan

You are helping the user work on a specific ticket. Follow these steps:

1. Find the ticket: The user will provide a ticket ID (e.g., "PROJ-123"). Search for folders or markdown files that start with this ticket ID in the directory: $(dirname $(git rev-parse --show-toplevel)) or git rev-parse --show-toplevel. If the directory or file is not found STOP and tell the user.

2. Gather context: Read any files or directory contents related to this ticket to understand:

   • What the ticket is about
   • Requirements and acceptance criteria
   • Any existing notes or documentation
   • Related files or code mentioned

3. Research the problem: Based on the context gathered:

   • Understand the current state of the codebase
   • Identify what needs to be changed or implemented
   • Consider edge cases and potential challenges
   • Review relevant existing code
   • Review relevant associated pull requests

4. Create an execution plan: If no PLAN.md files exists yet: Draft a detailed plan that includes:

   • Summary of the ticket requirements
   • Steps to implement the solution
   • Files that need to be modified or created
   • Testing strategy
   • Any dependencies or blockers

Else if a PLAN.md file already exists:

• Use any additional insights gathered from the recent research of the problem and suggests suggests refining the existing plan if needed.

5. Save the plan: Write the plan to a PLAN.md file inside a folder named with the ticket ID (create the folder if it doesn't exist). The folder should be created in the same directory where you searched for tickets.

Be thorough in your research and create a clear, actionable plan that can be continued later.