task-details

# Task Details Enrichment Skill

Automatically enrich Jira tasks with comprehensive context, technical requirements, dependencies, and estimates.

## When to Use

- Issue lacks sufficient detail for implementation
- Need to extract hidden requirements from descriptions
- Analyzing issue complexity for estimation
- Identifying dependencies and blockers
- Converting vague requirements into technical details
- Preparing issues for sprint planning

## Core Capabilities

| Capability | Purpose |
|-----------|---------|
| Context Extraction | Parse requirements, acceptance criteria, constraints |
| Dependency Mapping | Identify linked issues, code deps, team deps, blockers |
| Complexity Assessment | Estimate story points, risk factors, historical comparison |
| Requirement Decomposition | Break down epics, extract criteria, identify edge cases |
| Historical Analysis | Find similar resolved issues, extract patterns |

## Decision Tree

```
Analyze Issue
├─ Epic? → Epic Decomposition
├─ Missing Criteria? → Acceptance Criteria Extraction
├─ Unclear Complexity? → Complexity Analysis
├─ Unknown Dependencies? → Dependency Mapping
├─ Unclear Technical Approach? → Technical Design
├─ Missing Tests? → Test Case Generation
└─ Sprint Context Needed? → Sprint Context Analysis
```

## Epic Decomposition

**When:** Epic type, vague requirements, multi-sprint work

**Process:**
1. Extract business objectives and success metrics
2. Identify user journeys and personas
3. Break into stories with acceptance criteria
4. Map story dependencies
5. Create phased roadmap

**Example Output:**
```markdown
# Epic Decomposition: EPIC-001

## Business Objectives
- Primary goal: [What problem solved?]
- Success metrics: [ROI/impact?]

## Stories by Phase
### Phase 1: Foundation (Sprint 1)
- STORY-001: [Title] (5 pts) → Depends on [deps]
- STORY-002: [Title] (3 pts)

### Phase 2: Core (Sprint 2-3)
- STORY-003: [Title] (8 pts) → Depends on STORY-001

## Dependency Graph
STORY-001 → STORY-003 → STORY-0