Project Management Prompts: Agile, Scrum & Planning Templates

Generate sprint goals for our upcoming 2-week sprint:

TEAM CONTEXT:
- Team Size: [NUMBER] engineers
- Velocity: [STORY POINTS] per sprint
- Current Focus: [PRODUCT AREA]

CANDIDATE BACKLOG ITEMS:
[LIST YOUR TOP PRIORITY ITEMS]

Generate:
1. 2-3 sprint goal options (outcome-focused, not task-focused)
2. Recommended items for each goal
3. Story point estimates
4. Dependencies to resolve before sprint
5. Risks and mitigation strategies
6. Definition of Done for the sprint

Goals should be:
- Measurable and specific
- Achievable within the sprint
- Valuable to users/stakeholders
- Team-aligned

Help me plan sprint capacity:

TEAM MEMBERS:
[Name 1]: [ROLE] - [AVAILABILITY: 100%/80%/50%]
[Name 2]: [ROLE] - [AVAILABILITY]
...

SPRINT DETAILS:
- Sprint Length: [2 weeks]
- Holidays/PTO: [LIST DAYS OFF]
- Meetings: [RECURRING MEETINGS]

Calculate:
1. Total available hours per person
2. Recommended capacity (account for interruptions, bugs)
3. Story points target based on historical velocity
4. Buffer recommendation for unexpected work
5. Risk factors that might affect capacity

Output a capacity table and recommended sprint commitment.

Create a user story for this feature:

FEATURE: [DESCRIBE THE FEATURE]
USER TYPE: [WHO WILL USE IT]
BUSINESS GOAL: [WHY IT MATTERS]

Generate:
1. User Story (As a... I want... So that...)
2. Acceptance Criteria (Given/When/Then format)
   - Happy path scenarios
   - Edge cases
   - Error states
3. Technical Notes
   - Implementation considerations
   - API changes needed
   - Database changes
4. Story Points Estimate (with reasoning)
5. Dependencies
6. Questions for Product/Design

Format for Jira/Linear import.

Break down this epic into user stories:

EPIC: [EPIC TITLE]
DESCRIPTION: [WHAT IT ACCOMPLISHES]
TIMELINE: [TARGET COMPLETION]

Create:
1. List of 5-10 user stories that comprise this epic
2. For each story:
   - Title
   - Brief description
   - Rough size (S/M/L)
   - Dependencies on other stories
3. Suggested implementation order
4. MVP vs Nice-to-have classification
5. Stories that could be parallelized
6. Integration/testing stories needed

Keep stories small enough to complete in 1-3 days.

Generate retrospective discussion topics for:

SPRINT SUMMARY:
- Sprint Goal: [WHAT WE AIMED FOR]
- Outcome: [MET/PARTIALLY MET/MISSED]
- Key Events: [NOTABLE THINGS THAT HAPPENED]

TEAM CONTEXT:
- Team Size: [NUMBER]
- Recent Changes: [NEW MEMBERS, PROCESS CHANGES]
- Current Challenges: [KNOWN ISSUES]

Generate:
1. "What went well" prompts (5 specific questions)
2. "What could improve" prompts (5 specific questions)
3. "Action items from last retro" - review format
4. One creative/fun activity option
5. Timeboxing suggestions (90 min total)
6. Anonymous feedback questions

Make questions specific to our context, not generic.

Convert this retro feedback into action items:

FEEDBACK COLLECTED:
What went well:
[LIST ITEMS]

What could improve:
[LIST ITEMS]

Create:
1. Prioritized action items (max 3 per sprint)
2. For each action item:
   - Clear description
   - Owner assignment criteria
   - Success metric
   - Due date recommendation
   - How to verify completion
3. Items to defer vs. act on now
4. Quick wins vs. bigger initiatives
5. Follow-up schedule

Format as a table for easy tracking.