jira-retro
Patterns and templates for creating sprint/project retrospective reports from Jira data with time tracking and blocker analysis.
What this skill does
# Jira Retrospective Skill
This skill provides patterns, templates, and best practices for generating insightful retrospective reports from Jira project data.
## Overview
Retrospectives help teams reflect on completed work, identify patterns, and continuously improve. This skill focuses on data-driven retrospectives that analyze:
- Completed tickets and delivery metrics
- Time tracking and estimation accuracy
- Blockers and impediments
- Team productivity and patterns
## Report Template
### Full Retrospective Report
```markdown
# {Sprint/Project} Retrospective
**Period:** {start_date} to {end_date}
**Project:** {project_name} ({project_key})
**Generated:** {current_date}
---
## Executive Summary
{Brief overview - 2-3 paragraphs summarizing:
- What was accomplished
- Key metrics and trends
- Major wins and challenges}
### Key Metrics
- **Tickets Completed:** {count}
- **Story Points Delivered:** {points} (if tracked)
- **Total Time Logged:** {hours}h
- **Average Resolution Time:** {days} days
- **Blocked Issues:** {count} ({percentage}%)
- **Estimation Accuracy:** {percentage}% within ±20%
### Highlights
- ✅ {Major achievement or success}
- ✅ {Positive trend or improvement}
- ⚠️ {Challenge or area needing attention}
---
## Completed Tickets
### Summary Table
| Ticket | Summary | Type | Assignee | Status | Time Logged | Resolved |
|--------|---------|------|----------|--------|-------------|----------|
| {KEY-1} | {title} | {type} | {name} | {status} | {hours}h | {date} |
| {KEY-2} | {title} | {type} | {name} | {status} | {hours}h | {date} |
**Total Completed:** {count} issues
### Distribution by Type
- **Stories:** {count} ({percentage}%)
- **Bugs:** {count} ({percentage}%)
- **Tasks:** {count} ({percentage}%)
- **Other:** {count} ({percentage}%)
### Distribution by Priority
- **Critical/High:** {count} ({percentage}%)
- **Medium:** {count} ({percentage}%)
- **Low:** {count} ({percentage}%)
---
## Time Analysis
### Time Logged vs Estimated
| Ticket | Summary | Original Estimate | Actual Time | Variance | % Diff | Assignee |
|--------|---------|-------------------|-------------|----------|--------|----------|
| {KEY-1} | {title} | {hours}h | {hours}h | {±hours}h | {±%}% | {name} |
| {KEY-2} | {title} | {hours}h | {hours}h | {±hours}h | {±%}% | {name} |
**Totals:**
- **Original Estimates:** {total}h
- **Actual Time Logged:** {total}h
- **Total Variance:** {±hours}h ({±percentage}%)
### Time by Team Member
| Team Member | Issues Completed | Time Logged | Avg per Issue | % of Total |
|-------------|------------------|-------------|---------------|------------|
| {Name 1} | {count} | {hours}h | {avg}h | {%}% |
| {Name 2} | {count} | {hours}h | {avg}h | {%}% |
### Estimation Accuracy
**Categories:**
- ✅ **Accurate (±20%):** {count} tickets ({percentage}%)
- ⬆️ **Over-estimated (>20%):** {count} tickets ({percentage}%)
- ⬇️ **Under-estimated (>20%):** {count} tickets ({percentage}%)
- ❓ **No estimate:** {count} tickets ({percentage}%)
**Analysis:**
{Insights about estimation patterns:
- Which types of work are consistently over/under-estimated?
- Are certain team members more/less accurate?
- What factors might explain large variances?}
---
## Blocker Analysis
### Blocked Issues Detail
| Ticket | Summary | Blocked By | Date Blocked | Date Unblocked | Days Blocked | Impact |
|--------|---------|------------|--------------|----------------|--------------|--------|
| {KEY-1} | {title} | {reason} | {date} | {date} | {count} | {impact} |
| {KEY-2} | {title} | {reason} | {date} | {date} | {count} | {impact} |
**Summary Statistics:**
- **Total Blocked Issues:** {count} ({percentage}% of all issues)
- **Average Block Duration:** {days} days
- **Longest Block:** {days} days ({ticket_key})
- **Total Days Lost to Blockers:** {count} days
### Common Blocker Categories
1. **{Category 1}** - {count} issues
- Example: {description}
- Impact: {impact_description}
2. **{Category 2}** - {count} issues
- Example: {description}
- Impact: {impact_description}
3. **{Category 3}** - {count} issues
- Example: {description}
- Impact: {impact_description}
**Insights:**
{Analysis of blocking patterns:
- What are the most common causes of blockers?
- Are blockers increasing/decreasing over time?
- Which types of issues get blocked most often?
- Recommendations for reducing blockers}
---
## Retrospective Insights
### 🌟 What Went Well
**Wins and Successes:**
- {Specific achievement with data/metric}
- {Positive pattern observed}
- {Team strength or improvement}
**Why it worked:**
{Analysis of what contributed to success}
### 🔧 What Could Be Improved
**Challenges and Opportunities:**
- {Challenge 1 with specific example}
- **Impact:** {how this affected the team/project}
- **Suggestion:** {specific improvement idea}
- {Challenge 2 with specific example}
- **Impact:** {how this affected the team/project}
- **Suggestion:** {specific improvement idea}
- {Challenge 3 with specific example}
- **Impact:** {how this affected the team/project}
- **Suggestion:** {specific improvement idea}
### 📋 Action Items
**Immediate Actions (Next Sprint):**
- [ ] {Specific, measurable action item 1}
- Owner: {name}
- Target: {date/sprint}
- [ ] {Specific, measurable action item 2}
- Owner: {name}
- Target: {date/sprint}
**Long-term Improvements:**
- [ ] {Strategic improvement 1}
- Owner: {name}
- Timeline: {timeframe}
### 💡 Team Observations
**Velocity and Throughput:**
{Analysis of team capacity and flow}
**Collaboration Patterns:**
{Observations about teamwork, dependencies, knowledge sharing}
**Process Effectiveness:**
{Insights about workflow, ceremonies, tools}
---
## Appendix
### Methodology
**Data Collection:**
- **Source:** Jira {instance_url}
- **Project:** {project_key}
- **Query Period:** {start_date} to {end_date}
- **Completion Criteria:** Issues with status = "Done" and resolutiondate in range
- **Worklog Filter:** Logs with started date in range
**Metrics Calculated:**
- **Time Logged:** Sum of all worklog timeSpent in period
- **Estimation Variance:** (Actual - Estimate) / Estimate × 100
- **Block Duration:** Days between blocked status change and unblocked status change
- **Resolution Time:** Days from created to resolutiondate
### Data Quality Notes
{Any caveats or limitations:
- Missing time tracking data
- Incomplete estimates
- Status workflow variations
- Manual adjustments made}
### Raw Data
**JQL Queries Used:**
```
{List the actual JQL queries used to fetch data}
```
**Issues Analyzed:** {count}
**Worklogs Processed:** {count}
**Date Range Verified:** {confirmation}
---
*Generated by Claude Code with aai-pm-jira plugin*
```
---
## Metrics Guide
### Essential Metrics
| Metric | Calculation | Purpose |
|--------|-------------|---------|
| **Tickets Completed** | Count of issues with status = Done in period | Throughput |
| **Total Time Logged** | Sum of worklog timeSpent in period | Effort tracking |
| **Avg Resolution Time** | Average of (resolutiondate - created) | Cycle time |
| **Estimation Variance** | (Actual - Estimate) / Estimate | Estimation accuracy |
| **Blocked Issues %** | (Blocked issues / Total issues) × 100 | Flow efficiency |
### Advanced Metrics
| Metric | Calculation | Purpose |
|--------|-------------|---------|
| **Lead Time** | Time from created to done | Full delivery time |
| **Cycle Time** | Time from in progress to done | Active work time |
| **Throughput** | Issues completed per time period | Team capacity |
| **WIP** | Issues in progress at period end | Work in progress |
| **Flow Efficiency** | (Active time / Total time) × 100 | Process efficiency |
---
## JQL Patterns for Retrospectives
### Basic Queries
```jql
# All completed issues in date range (by project)
project = PROJ AND status = Done AND resolutiondate >= "2024-01-01" AND resolutiondate <= "2024-01-31"
# All completed issues in date range (by filter ID)
filter =Related in Data & Analytics
clawarr-suite
IncludedComprehensive management for self-hosted media stacks (Sonarr, Radarr, Lidarr, Readarr, Prowlarr, Bazarr, Overseerr, Plex, Tautulli, SABnzbd, Recyclarr, Unpackerr, Notifiarr, Maintainerr, Kometa, FlareSolverr). Deep library exploration, analytics, dashboard generation, content management, request handling, subtitle management, indexer control, download monitoring, quality profile sync, library cleanup automation, notification routing, collection/overlay management, and media tracker integration (Trakt, Letterboxd, Simkl).
querying-soql
IncludedSOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
habit-flow
IncludedAI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
visualizing-data
IncludedBuilds dashboards, reports, and data-driven interfaces requiring charts, graphs, or visual analytics. Provides systematic framework for selecting appropriate visualizations based on data characteristics and analytical purpose. Includes 24+ visualization types organized by purpose (trends, comparisons, distributions, relationships, flows, hierarchies, geospatial), accessibility patterns (WCAG 2.1 AA compliance), colorblind-safe palettes, and performance optimization strategies. Use when creating visualizations, choosing chart types, displaying data graphically, or designing data interfaces.