ticket-planning-workflow

# Ticket Planning Workflow Skill

Transform Linear tickets into actionable implementation plans through systematic investigation and collaborative planning.

## Purpose

Transform uncertainty into clarity by:
- Gathering complete ticket context from Linear
- Exploring relevant codebase sections
- Identifying patterns and conventions
- Asking targeted clarifying questions
- Creating detailed, actionable implementation plans

## Planning Methodology

### Phase 1: Ticket Intelligence Gathering

#### Fetch and Parse Ticket

```bash
# Get complete ticket information
mcp__linear__get_issue --id "$ticket_id"
```

#### Extract Structured Information

Parse from ticket:
- **Type**: Feature/Bug/Chore (from labels)
- **Priority**: Urgency level
- **Acceptance Criteria**: From description checkboxes
- **Related Context**: Parent tickets, dependencies, blockers
- **Discussion Points**: Key decisions from comments

#### Identify Unclear Items

Flag for clarification:
- Ambiguous requirements
- Missing acceptance criteria
- Architectural decisions needed
- Scope boundaries unclear

### Phase 2: Deep Codebase Exploration

#### Step 1: Broad Search

```bash
# Find existing related code
rg "keyword" --type ts --files-with-matches

# Find similar implementations
rg "pattern-keyword" --type ts -A 5
```

#### Step 2: Understand Architecture

For each relevant file:
- Document current implementation
- Note patterns used
- Identify extension points
- Check for project-specific requirements

#### Step 3: Find Patterns to Follow

Extract from codebase:
- **Error handling**: Common patterns
- **Entity pattern**: Data structures
- **Route pattern**: API organization
- **Service pattern**: Business logic organization

#### Step 4: Check Project Guidelines

```bash
# Review CLAUDE.md for requirements
cat CLAUDE.md | grep -A 10 "relevant-section"
```

### Phase 3: Collaborative Clarification

#### Question Framework

Present 2-4 questions at a time with:
- **Context**: What you found in codebase