jira-ticket-analysis

# Jira Ticket Analysis Skill

This skill provides methodology for analyzing Jira ticket quality and identifying areas for improvement.

## Quality Dimensions

### 1. Clarity
**Questions to assess**:
- Is the goal obvious from the summary?
- Is the description free of jargon?
- Would a new team member understand this?
- Are acronyms explained?

**Scoring**:
- 5: Crystal clear, no questions needed
- 4: Clear with minor ambiguity
- 3: Understandable but needs context
- 2: Confusing, multiple interpretations
- 1: Cannot understand the request

### 2. Completeness
**Questions to assess**:
- Are acceptance criteria defined?
- Is the scope clear (what's in/out)?
- Are dependencies listed?
- Is technical context provided?

**Scoring**:
- 5: All information present, ready to implement
- 4: Minor details missing
- 3: Key information missing but discoverable
- 2: Significant gaps
- 1: Missing most required information

### 3. Actionability
**Questions to assess**:
- Can work start immediately?
- Are blockers identified and addressed?
- Is the scope achievable?
- Are success criteria measurable?

**Scoring**:
- 5: Can start now with confidence
- 4: One small clarification needed
- 3: Some research/clarification needed
- 2: Blocked or unclear how to proceed
- 1: Cannot start without major discovery

### 4. Context
**Questions to assess**:
- Is the "why" explained?
- Is user impact described?
- Are related tickets linked?
- Is there technical background?

**Scoring**:
- 5: Full context, understand importance
- 4: Good context, minor gaps
- 3: Basic context provided
- 2: Little context, unclear importance
- 1: No context, don't know why this matters

---

## Analysis Process

### Step 1: Initial Read
- Read summary and description
- Note first impressions
- Identify obvious issues

### Step 2: Score Dimensions
Rate each dimension 1-5 and note specific issues:

```markdown
| Dimension | Score | Issues |
|-----------|-------|--------|
| Clarity | 3 | Acronyms undefined, vague scope