start-ticket

name: start-ticket description: Plan and prepare work on a ticket. Creates a git branch, reads ticket context (via browser or local files), explores relevant code, and produces an implementation plan with progress notes.

Start Ticket

Begin work on a ticket by fetching context, exploring code, and creating a plan.

Instructions

When invoked with a ticket number (e.g., /start-ticket PROJ-123):

1. Read Ticket Context

If .claude/tickets/{TICKET}/ folder exists:

• Read all files in the folder (description.md, progress.md, attachments)
• Summarize the ticket in 3-5 bullet points: what needs to change and why
• Skip to step 3 (branch creation)

If the folder does NOT exist — fetch via browser (Chrome extension):

1. Call tabs_context_mcp to get available browser tabs
2. Look for an existing tab on your ticket system — reuse it if found
3. If no tab exists, create one with tabs_create_mcp
4. Navigate to the ticket URL (Jira, Linear, GitHub Issues, etc.)
5. Use get_page_text to extract:
   • Title, description, acceptance criteria
   • Priority, status, assignee
   • Relevant comments
6. Create the folder: .claude/tickets/{TICKET}/
7. Create description.md with extracted content:

# {TICKET}: {Title}

## Description
{description from ticket system}

## Acceptance Criteria
{acceptance criteria, if present}

## Linked Issues
- {LINKED-TICKET}: {title} - {status} ({link type})

## Comments
{relevant comments}

## Additional Context
{anything else relevant}

8. Summarize the ticket in 3-5 bullet points

2. Determine Base Branch

• Check .claude/current-sprint.md for the current base branch
• If unclear, default to main (or ask the user)
• Verify the base branch exists: git ls-remote --heads origin {base-branch}

3. Create Git Branch

• Fetch and sync the base branch: git fetch origin {base-branch} && git checkout {base-branch} && git pull origin {base-branch}
• Create the ticket branch: git checkout -b feature/{TICKET}-{brief-description}

4. Explore Relevant Code

• Follow code pointers from the ticket description
• Search for related files using Glob and Grep
• Check CLAUDE.md for project context and recently active areas
• Identify the scope of changes needed

5. Plan Implementation

• Create a task list with clear steps
• Flag any decisions or trade-offs that need user input
• Identify files that will be created or modified (list full paths)
• Note dependencies on other tickets or systems

6. Create Progress File

Create .claude/tickets/{TICKET}/progress.md:

# {TICKET}: {Title}

## Status: PLANNING

## Summary
- Brief description of what needs to be implemented

## Branch
`feature/{TICKET}-{brief-description}` (from `{base-branch}`)

## Implementation Plan
1. Step-by-step plan with file paths

## Files to Modify
- `path/to/file` - what changes and why

## Findings & Research
- Key discoveries from code exploration
- Relevant patterns found in existing code

## Questions
- Anything unclear from the ticket
- Design decisions that need input

7. STOP - Review Plan with User

Do NOT start coding. Present the implementation plan and wait for user review:

• Ticket: number and title
• Branch: the created branch name
• Changes needed: list of files and what changes in each
• Open questions: anything unclear from the ticket
• Next steps: what to do first when implementation begins

Only proceed to implementation after the user reviews and approves the plan.

Important

• Do NOT start coding - this skill is for understanding and planning only
• Ask the user before making any design decisions with multiple valid approaches
• If the ticket references other tickets or PRs, note the dependencies
• Follow your project's commit message convention
• NEVER add Co-Authored-By or AI attribution to commits (unless your team wants it)