jira-status-sync

# Jira Status Sync Skill

This skill provides patterns for keeping Jira tickets synchronized with actual development progress, ensuring accurate tracking and reporting.

## Why Status Sync Matters

- Accurate sprint burndowns
- Realistic progress visibility
- Better blockers identification
- Improved team coordination
- Reliable velocity metrics

---

## Status Update Triggers

### When to Update Status

| Event | Status Change | Comment |
|-------|--------------|---------|
| Assigned to you | → In Progress (or keep Open) | Note approach |
| Started coding | → In Progress | Brief plan |
| PR created | → Code Review | Link to PR |
| PR approved | → Ready for QA (if applicable) | Note reviewer |
| Tests passed | → Done | Summary of changes |
| Blocked | Keep current + add Blocker flag | Blocker details |
| Unblocked | Remove Blocker flag | Resolution note |

### When to Add Comments

- Starting work (approach/plan)
- Significant progress milestones
- Encountering blockers
- Scope changes or discoveries
- Questions needing answers
- PR ready for review
- Work completed

---

## Status Transitions

### Common Workflow

```
To Do ─────────────────────────────────────────────────────┐
   │                                                        │
   ▼                                                        │
In Progress ──► Code Review ──► QA ──► Done                │
   │                │           │                          │
   │ (blocked)      │           │                          │
   ▼                ▼           ▼                          │
Blocked ────────────────────────────────────────────────────┘
   (returns to previous status when unblocked)
```

### Transition Comments

**To In Progress**:
```
Starting implementation. Approach:
- [Key step 1]
- [Key step 2]

Estimated completion: [Date]
```

**To Code Review**:
```
PR ready for review: [PR Link]

Changes:
- [Summary of changes]

Testing done:
- [Tests written/run]
```

**To Done**:
```
Completed and merged. Ch