Skip to content

feat: Add JIRA retrospective reporting to aai-pm-jira plugin#1

Merged
bradtaylorsf merged 3 commits into
mainfrom
jira-retro
Feb 4, 2026
Merged

feat: Add JIRA retrospective reporting to aai-pm-jira plugin#1
bradtaylorsf merged 3 commits into
mainfrom
jira-retro

Conversation

@spindle79
Copy link
Copy Markdown
Contributor

Summary

Adds comprehensive retrospective report generation capabilities to the aai-pm-jira plugin with time tracking and blocker analysis.

Features

New Command: /jira-retro

  • Generate sprint/project retrospective reports from Jira data
  • Support for project-based (e.g., PROJ) or account-based (e.g., user@example.com) analysis
  • Interactive mode prompts for missing parameters
  • Outputs detailed markdown reports

Analysis Includes

  • Completed Tickets Summary - Status, assignee, resolution time, distribution by type/priority
  • Time Tracking Analysis - Total time logged per ticket, estimated vs actual comparison, time by team member
  • Blocker Analysis - Blocked issues with duration, common blocker categories, recommendations
  • Retrospective Insights - What went well, improvement areas, actionable items with owners

Components Added

  1. Agent: jira-retro-agent.md

    • Queries Jira using JQL for completed issues and worklogs
    • Analyzes patterns in time tracking and blockers
    • Generates markdown reports with insights
  2. Skill: jira-retro/SKILL.md

    • Comprehensive templates for retrospective reports
    • JQL patterns for project and account-based queries
    • Metrics guide and best practices
    • Report variations (sprint, epic, personal retros)
  3. Command: jira-retro.md

    • User-invokable interface
    • Argument parsing for project/account, dates, output file
    • Help documentation and examples

Usage Examples

# Project-based retrospective
/jira-retro PROJ 2024-01-01 2024-01-31

# Account-based retrospective
/jira-retro john.doe@company.com 2024-01-01 2024-01-31

# Interactive mode (prompts for all parameters)
/jira-retro

Version Updates

  • aai-pm-jira plugin: 1.0.01.1.0
  • Marketplace: 1.0.21.0.3
  • Added keywords: retrospective, time-tracking
  • Updated descriptions to mention retrospective capabilities

Testing

✅ Plugin structure validated with node scripts/validate-plugins.js
✅ Manifests updated and regenerated
✅ All files follow Claude Code plugin standards

To Test

# Start Claude with the plugin
claude --plugin-dir ./plugins/aai-pm-jira

# Test the command
/jira-retro

Prerequisites: Atlassian MCP server configured with valid Jira credentials

Files Changed

  • plugins/aai-pm-jira/agents/jira-retro-agent.md (new)
  • plugins/aai-pm-jira/commands/jira-retro.md (new)
  • plugins/aai-pm-jira/skills/jira-retro/SKILL.md (new)
  • 📝 plugins/aai-pm-jira/.claude-plugin/plugin.json (version bump, keywords)
  • 📝 .claude-plugin/marketplace.json (version bump, description update)
  • 📝 plugin-manifest.json (regenerated)

🤖 Generated with Claude Code

spindle79 and others added 3 commits February 4, 2026 10:47
Add comprehensive retrospective report generation with time tracking analysis.

Features:
- /jira-retro command for generating sprint/project retrospectives
- Support for project-based or account-based analysis
- Time tracking analysis (logged vs estimated time)
- Blocker analysis with duration and patterns
- Completed tickets summary with metrics
- Actionable insights and recommendations
- Markdown report output with detailed sections

Components:
- jira-retro-agent: Queries Jira, analyzes data, generates reports
- jira-retro skill: Templates and patterns for retrospective reports
- jira-retro command: User-invokable /jira-retro interface

Plugin Updates:
- Bumped aai-pm-jira version from 1.0.0 to 1.1.0
- Updated marketplace version from 1.0.2 to 1.0.3
- Added keywords: retrospective, time-tracking
- Regenerated plugin-manifest.json

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Simplify retrospective functionality to focus on project-based analysis only.

Changes:
- Removed account/email input option from agent
- Updated command to only accept project keys
- Removed account-based JQL patterns from skill
- Removed personal retrospective template
- Simplified parameter collection workflow

The tool now only generates retrospectives for Jira projects, not individual accounts.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Add ability to use saved Jira filters as alternative to project keys.

Features:
- Support filter ID (e.g., 12345)
- Support filter name (e.g., "My Sprint Issues")
- JQL patterns for filter-based queries
- Filter-based retrospective template
- Examples and troubleshooting for filters

Usage:
- /jira-retro PROJ 2024-01-01 2024-01-31 (project-based)
- /jira-retro 12345 2024-01-01 2024-01-31 (filter ID)
- /jira-retro "My Filter" 2024-01-01 2024-01-31 (filter name)

This allows users to leverage existing saved filters for complex
issue queries and cross-project retrospectives.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@bradtaylorsf bradtaylorsf self-assigned this Feb 4, 2026
@bradtaylorsf bradtaylorsf merged commit 685c62d into main Feb 4, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants