القائمة
Assist with sprint planning, backlog grooming, story point estimation, and sprint capacity management. Use when planning sprints, estimating work, organizing backlog, or when user mentions sprint planning, velocity, capacity, or story points.
Create and maintain Architecture Decision Records (ADRs) in Confluence. Use when documenting technical decisions, architecture choices, technology selections, or when user mentions ADR, architecture decisions, technical choices, or design decisions.
Generate comprehensive API documentation for Confluence from code, OpenAPI specs, or endpoints. Use when documenting REST APIs, GraphQL APIs, or any API endpoints. Creates structured documentation with examples, parameters, responses, and error codes.
Convert Markdown content to Confluence's ADF (Atlassian Document Format) for creating and updating pages. Use when creating Confluence pages from README files, documentation, or any Markdown content. Handles headings, lists, code blocks, tables, links, and more.
Generate comprehensive release notes for Confluence from Jira issues, git commits, and pull requests. Use when preparing releases, creating changelogs, documenting version updates, or when user mentions release notes, changelog, version, or release documentation.
Create well-structured Jira issues from code changes, conversations, or requirements. Use when creating issues, bugs, stories, tasks, or when the user wants to track work in Jira. Analyzes context to generate clear titles, descriptions, and appropriate fields.
Build and optimize JQL (Jira Query Language) queries for searching issues. Use when the user needs to search Jira issues, filter by complex criteria, find specific bugs or features, or when they mention JQL, queries, or searching Jira.
| name | Sprint Planning Assistant |
| description | Assist with sprint planning, backlog grooming, story point estimation, and sprint capacity management. Use when planning sprints, estimating work, organizing backlog, or when user mentions sprint planning, velocity, capacity, or story points. |
| allowed-tools | Bash |
Expert assistance for planning sprints, estimating work, and managing team capacity.
sprint = "Sprint 42" ORDER BY updated DESC
Analyze:
project = PROJ AND sprint IS EMPTY AND status = "To Do" ORDER BY priority DESC
Verify:
Example Goals:
Formula:
Capacity = (Team Size × Work Days × Hours per Day) - (Meetings + PTO + Buffer)
Example:
Team: 5 developers
Sprint: 10 work days
Work: 6 hours/day (accounting for meetings)
PTO: 2 days (one person out)
Buffer: 20% (for unexpected work)
Capacity = (5 × 10 × 6) - (2 × 6) - (20% of 288)
= 300 - 12 - 58
= 230 hours
Or in story points (if velocity is 40):
Capacity ≈ 40 story points
Criteria:
Query for candidates:
project = PROJ
AND status = "To Do"
AND sprint IS EMPTY
AND "Story Points" IS NOT EMPTY
ORDER BY priority DESC, rank ASC
Story points measure relative effort/complexity, not time:
1 - Trivial: Simple change, < 1 hour
2 - Easy: Small feature, well understood
3 - Moderate: Standard feature, clear path
5 - Average: Typical feature, some complexity
8 - Complex: Significant feature, multiple components
13 - Very Complex: Large feature, high uncertainty
21 - Epic: Too large, should be split
XS = 1 point
S = 2 points
M = 3 points
L = 5 points
XL = 8 points
Compare to previously completed work:
Estimate = (Optimistic + (4 × Most Likely) + Pessimistic) / 6
Example:
Best case: 3 points
Most likely: 5 points
Worst case: 13 points
Estimate = (3 + (4 × 5) + 13) / 6 = 36 / 6 = 6 points
For each story:
Base Hours = Team Size × Sprint Days × Hours/Day
Actual Hours = Base - (PTO + Meetings + Support + Buffer)
Percentage of time spent on sprint work:
Typical: 60-70%
High performing: 70-80%
New team: 50-60%
Average story points completed per sprint:
Velocity = Average(Last 3-5 Sprints)
Team Details:
Commitments:
Calculation:
Base capacity: 45 points (historical velocity)
Adjustments:
- PTO: -3 days of 1 person = -3 points
- Training: -2 days of 2 people = -4 points
- On-call: -20% of 1 person = -2 points
- Buffer (10%): -4 points
Sprint capacity: 45 - 3 - 4 - 2 - 4 = 32 points
Loading 60 points when velocity is 40.
Fix: Use historical velocity as guide, add buffer
Loading 20 points when velocity is 40, to "guarantee" completion.
Fix: Commit to realistic amount, have stretch goals ready
Just a collection of random stories.
Fix: Define clear, valuable objective for the sprint
Constantly splitting stories after sprint starts.
Fix: Better grooming and estimation up front
Starting work that's blocked by external factors.
Fix: Identify dependencies during planning
Adding unplanned features during implementation.
Fix: Stick to acceptance criteria, capture new ideas as separate stories
project = PROJ
AND type = Story
AND status = "To Do"
AND sprint IS EMPTY
AND "Story Points" IS NOT EMPTY
AND description IS NOT EMPTY
ORDER BY priority DESC
sprint in openSprints()
ORDER BY status ASC, priority DESC
project = PROJ
AND type IN (Story, Task)
AND "Story Points" IS EMPTY
AND status != Done
ORDER BY priority DESC
sprint = "Sprint 42"
AND status IN ("In Progress", "To Do")
sprint = "Sprint 42"
AND sprint = "Sprint 43"
AND resolution IS EMPTY
Method 1: Average of Last 3 Sprints
Sprint 40: 38 points
Sprint 41: 42 points
Sprint 42: 44 points
Velocity = (38 + 42 + 44) / 3 = 41 points
Method 2: Weighted Average
Recent sprints count more:
Velocity = (Sprint N × 3 + Sprint N-1 × 2 + Sprint N-2 × 1) / 6
Velocity: Historical output (story points completed) Capacity: Theoretical input (available hours/points)
Use velocity for sprint planning, not capacity.
Sprint Number: 43
Duration: Jan 15 - Jan 28 (10 work days)
Sprint Goal: Complete user profile functionality
Team Velocity: 41 points (average last 3 sprints)
Team Members: 6 developers
Availability:
- Alice: 10 days (full)
- Bob: 7 days (3 days PTO)
- Carol: 10 days (full)
- Dave: 10 days (full)
- Eve: 9 days (1 day training)
- Frank: 10 days (full, but on-call)
Adjusted Capacity: 36 points
Committed Stories (36 points):
- PROJ-101: User profile page (8 pts)
- PROJ-102: Avatar upload (5 pts)
- PROJ-103: Profile editing (8 pts)
- PROJ-104: Privacy settings (5 pts)
- PROJ-105: Profile completion badge (3 pts)
- PROJ-106: Update navigation (2 pts)
- PROJ-107: Profile tests (5 pts)
Stretch Goals (13 points):
- PROJ-108: Social media links (5 pts)
- PROJ-109: Custom themes (8 pts)
Dependencies:
- PROJ-102 blocked until design review (due Jan 16)
- PROJ-104 requires security review
Risks:
- Avatar upload may need third-party service
- Privacy settings have regulatory requirements
Mitigation:
- Start PROJ-101, 103, 106 first
- Spike for avatar service options
- Consult legal team early on privacy
Must Have:
- Users can view and edit their profiles
- Avatar upload working
- Privacy controls functional
Nice to Have:
- Profile completion indicators
- Social media integration
Definition of Done:
- Code reviewed
- Tests passing (>80% coverage)
- Deployed to staging
- Acceptance criteria met
- Documentation updated
When you need sprint planning assistance, I will:
You: "Help me plan Sprint 45. Team of 5, one person out for 2 days, velocity is usually around 35 points"
Me: "I'll help plan Sprint 45.
Capacity Calculation:
Let me search for ready stories:
[Uses /jira-search with refinement query]
Recommended Sprint Backlog (30 points):
Sprint Goal: Complete basic payment processing flow
Stretch Goals (if time allows):
Should I create these issues or adjust the selection?"