From aai-pm-jira
Provides patterns for Jira sprint planning including capacity calculation, ticket selection with JQL, API operations for sprint creation, and organization templates. Useful for agile team planning.
npx claudepluginhub bradtaylorsf/alphaagent-teamThis skill uses the workspace's default tool permissions.
This skill provides patterns for effective sprint planning using Jira, including capacity planning, ticket prioritization, and sprint organization.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
This skill provides patterns for effective sprint planning using Jira, including capacity planning, ticket prioritization, and sprint organization.
Backlog Grooming
Capacity Calculation
Team Velocity: [average points completed per sprint]
Available Days: [total team days - PTO - meetings]
Capacity: ~80% of velocity (buffer for unknowns)
Priority Review
Review Sprint Goal
Select Tickets
Validate Commitments
// POST /rest/agile/1.0/sprint
{
"name": "Sprint 42",
"startDate": "2024-01-15T09:00:00.000Z",
"endDate": "2024-01-29T17:00:00.000Z",
"originBoardId": 123,
"goal": "Complete user notification system"
}
// POST /rest/agile/1.0/sprint/{sprintId}/issue
{
"issues": ["PROJ-123", "PROJ-124", "PROJ-125"]
}
# Current sprint tickets
sprint in openSprints() AND project = PROJ
# Sprint backlog
sprint = "Sprint 42" AND project = PROJ ORDER BY rank
# Unassigned in sprint
sprint in openSprints() AND assignee IS EMPTY
# Blocked tickets
sprint in openSprints() AND labels = blocked
# Carry-over candidates
sprint in closedSprints() AND status != Done AND
updatedDate > startOfWeek(-1)
| Team Member | Days Available | Focus Areas | Notes |
|---|---|---|---|
| Developer 1 | 10 | Backend, API | |
| Developer 2 | 8 | Frontend | PTO: 2 days |
| Developer 3 | 10 | Full-stack | |
| Total | 28 days |
Historical Velocity: 40 points/sprint (average of last 3)
Team Availability: 90% this sprint
Adjusted Capacity: 36 points
Allocation:
- Features: 25 points (70%)
- Bugs: 7 points (20%)
- Tech Debt: 4 points (10%)
| Load Level | Description | Risk |
|---|---|---|
| < 70% | Under-committed | Low, may add mid-sprint |
| 70-85% | Optimal | Low |
| 85-95% | Full | Medium |
| > 95% | Over-committed | High, likely carry-over |
Examples:
To Do | In Progress | Code Review | QA | Done
| Column | Limit | Reason |
|---|---|---|
| In Progress | 2 per person | Focus |
| Code Review | 5 | Keep reviews flowing |
| QA | 3 | Prevent bottleneck |
Criteria for adding:
Process:
Criteria for removal:
Process:
| Metric | Healthy | Warning | Action Needed |
|---|---|---|---|
| Completion | > 85% | 70-85% | < 70% |
| Carry-over | < 10% | 10-20% | > 20% |
| Scope Change | < 15% | 15-25% | > 25% |
| Blocked Time | < 10% | 10-20% | > 20% |