AI Prompts Library

You are an experienced product owner and agile coach. Write comprehensive user stories with acceptance criteria for the described feature.

**Feature:** [DESCRIBE THE FEATURE]
**Product:** [PRODUCT_NAME]
**Sprint Goal:** [WHAT THIS SPRINT AIMS TO ACHIEVE]
**Users/Personas:** [WHO WILL USE THIS FEATURE]

**For each user story, provide:**

1. **Story Format:**
   As a [specific user role],
   I want to [action/capability],
   So that [business value/benefit].

2. **Acceptance Criteria** (Given/When/Then format):
   - Given [precondition]
   - When [action]
   - Then [expected result]
   - Write 3-7 acceptance criteria per story covering happy path and edge cases

3. **Story Metadata:**
   - Priority: Must-have / Should-have / Could-have / Won't-have (MoSCoW)
   - Story Points: Estimate using Fibonacci (1, 2, 3, 5, 8, 13)
   - Dependencies: Other stories this depends on
   - Labels: Frontend / Backend / Full-stack / Design / Infrastructure

4. **Technical Notes:**
   - Implementation hints (not prescriptive, but helpful context)
   - API endpoints needed
   - Database changes required
   - Third-party integrations

5. **Definition of Done:**
   - Code complete with tests
   - Code review approved
   - QA tested on staging
   - Documentation updated
   - Accessibility verified
   - Performance acceptable

**Story Splitting Guidance:**
- If a story is > 8 points, split it using these techniques:
  - By workflow step
  - By data variation
  - By business rule
  - By interface (API first, then UI)
  - By operation (CRUD: create first, then read, update, delete)

**Output**: A complete set of user stories for the feature, organized by priority, with a story map showing the user journey.

You are an experienced agile coach facilitating a sprint retrospective. Guide the team through a productive retrospective session and help generate actionable improvements.

**Sprint Details:**
- Sprint Number: [NUMBER]
- Sprint Duration: [X weeks]
- Team Name: [TEAM_NAME]
- Sprint Goal: [WAS_IT_ACHIEVED? YES/NO]
- Team Size: [NUMBER]
- Notable Events: [ANYTHING_SIGNIFICANT_THAT_HAPPENED]

**Sprint Metrics:**
- Planned Story Points: [X]
- Completed Story Points: [Y]
- Velocity Trend: [INCREASING / STABLE / DECREASING over last 3 sprints]
- Bugs Found: [NUMBER]
- Unplanned Work: [% of sprint capacity]
- Sprint Burndown: [ON_TRACK / STARTED_LATE / STALLED_MIDWAY / HOCKEY_STICK]

**Retrospective Framework** (Choose or let me suggest):
- Classic: What went well? / What did not go well? / What to improve?
- Sailboat: Wind (helping) / Anchor (slowing) / Rocks (risks) / Island (goal)
- 4Ls: Liked / Learned / Lacked / Longed for
- Start-Stop-Continue
- Mad-Sad-Glad

**Generate:**

1. **Icebreaker** (2 minutes):
   - A fun, relevant question to get the team talking

2. **Data Gathering** (10 minutes):
   - Prompt questions for each category in the chosen framework
   - Suggestions for common themes based on the sprint metrics

3. **Pattern Analysis** (10 minutes):
   - Identify recurring themes from past retrospectives
   - Connect sprint metrics to qualitative feedback
   - Highlight systemic issues vs. one-time problems

4. **Action Item Generation** (15 minutes):
   - For each identified improvement:
     - SMART action item (Specific, Measurable, Achievable, Relevant, Time-bound)
     - Owner (single person)
     - Definition of Done
     - How to verify improvement next sprint
   - Limit to 2-3 actions (focus over breadth)

5. **Follow-Up:**
   - Review of action items from last retrospective
   - Tracking template for improvement metrics
   - Suggested experiments for the next sprint

**Output**: Complete retrospective facilitation guide with timing, questions, analysis framework, and action item templates.

Write user story following Agile best practices:

**Epic**: [EPIC NAME]

**User Story**:
As a [USER ROLE]
I want to [ACTION/FEATURE]
So that [BENEFIT/VALUE]

**Acceptance Criteria** (Given-When-Then):
1. Given [CONTEXT], When [ACTION], Then [EXPECTED RESULT]
2. Given [CONTEXT], When [ACTION], Then [EXPECTED RESULT]
3. [ADD MORE AS NEEDED]

**Technical Notes**:
- Dependencies: [SYSTEMS/APIS]
- Edge Cases: [SCENARIOS]
- Performance: [REQUIREMENTS]

**Definition of Done**:
- [ ] Code complete & reviewed
- [ ] Unit tests (>80% coverage)
- [ ] Integration tests pass
- [ ] Documentation updated
- [ ] Acceptance criteria validated

**Story Points**: [ESTIMATE]
**Priority**: [HIGH/MEDIUM/LOW]