| Sheet 11: JIRA & TICKET MANAGEMENT (PMO) | ||||||||
| Category | Use Case | Prompt Template | Variables to Customize | Expected Output | Time Saved | Contributed By | Date Added | Rating |
| JIRA Management | JIRA ticket cleanup | I'm a Project Manager cleaning up JIRA tickets for [PROJECT_NAME]. Current ticket: Title="[CURRENT_TITLE]", Description="[CURRENT_DESCRIPTION]". Rewrite with: Clear, specific title (action-oriented), Detailed description (what needs to be done and why), Acceptance criteria (how we know it's done), Priority recommendation (with justification), Estimated story points (with rationale), Labels/tags for categorization. | PROJECT_NAME, CURRENT_TITLE, CURRENT_DESCRIPTION | Improved JIRA ticket | 10-15 min | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐⭐ |
| JIRA Management | Epic description | I'm a Project Manager creating an epic for [FEATURE_NAME] in [PROJECT_NAME]. Epic scope: [SCOPE_DESCRIPTION]. Write an epic description including: Business Value/Goal, High-Level Requirements, Success Metrics, Dependencies, Out of Scope, Estimated Timeline, Key Stakeholders. Clear, comprehensive, suitable for team and stakeholder reference. | FEATURE_NAME, PROJECT_NAME, SCOPE_DESCRIPTION | Epic description | 30-45 min | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐ |
| JIRA Management | Sprint retrospective summary | I'm a Project Manager summarizing sprint retrospective for Sprint [NUMBER]. Team feedback: [FEEDBACK_POINTS]. Organize into: What Went Well (3-5 items), What Didn't Go Well (3-5 items), Action Items for Next Sprint (with owners), Patterns or Trends, Shout-outs/Recognition. | SPRINT_NUMBER, FEEDBACK_POINTS | Retrospective summary | 20-30 min | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐ |
| JIRA Management | Backlog prioritization rationale | I'm a Project Manager documenting prioritization decisions for [PROJECT_NAME]. Criteria: [PRIORITIZATION_CRITERIA]. Backlog items: [ITEM_LIST]. For the top 10 prioritized items, provide brief rationale (2-3 sentences each) explaining: Why now, Business value, Dependencies considered, Risk factors. | PROJECT_NAME, PRIORITIZATION_CRITERIA, ITEM_LIST | Prioritization rationale | 45-60 min | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐ |
| JIRA Management | Velocity trend analysis | I'm a Project Manager analyzing velocity for [TEAM_NAME]. Historical data: [VELOCITY_DATA for past 6 sprints]. Analyze: Average velocity, Trend (increasing/decreasing/stable), Outlier sprints (with probable causes), Predictability (consistency), Recommended planning velocity for next sprint, Factors affecting velocity. | TEAM_NAME, VELOCITY_DATA | Velocity analysis | 30-45 min | Stephen Mitchell > Claude | 4-Feb | ⭐⭐⭐⭐ |