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 a senior product manager creating a strategic product roadmap. Design a comprehensive roadmap for the described product.

**Product:** [PRODUCT_NAME]
**Product Stage:** [Concept / MVP / Growth / Mature]
**Vision:** [LONG-TERM PRODUCT VISION]
**Time Horizon:** [6 months / 12 months / 18 months]
**Team Capacity:** [NUMBER of engineers, designers, PMs]
**Current Key Metrics:** [LIST METRICS AND VALUES]
**Strategic Priorities:** [LIST 2-3 COMPANY PRIORITIES]

**Generate a product roadmap with:**

1. **Now (Current Quarter):**
   - 3-5 features/initiatives actively in development
   - For each: User problem it solves, Expected impact on key metric, Effort estimate (T-shirt size), Dependencies, Success criteria

2. **Next (Next Quarter):**
   - 3-5 planned features/initiatives
   - For each: Strategic rationale, Target user segment, Key assumptions to validate, Required research or design work

3. **Later (Quarter 3+):**
   - 5-8 exploratory ideas on the horizon
   - For each: Strategic alignment, Open questions to answer, Market signals supporting this direction

4. **Prioritization Framework:**
   - RICE Score for each item (Reach x Impact x Confidence / Effort)
   - Stack rank based on RICE
   - Explain any overrides to the RICE ranking (strategic bets, dependencies)

5. **Theme Mapping:**
   - Group features into 3-4 strategic themes
   - Show how themes connect to company OKRs
   - Identify theme dependencies

6. **Roadmap Communication:**
   - Executive summary view (one page, no dates)
   - Engineering view (detailed with dependencies and milestones)
   - Customer-facing view (benefit-focused, no internal details)
   - Sales enablement view (competitive positioning of upcoming features)

7. **Review Process:**
   - Quarterly roadmap review cadence
   - Input sources (customer feedback, analytics, sales requests, support tickets)
   - Governance: Who approves roadmap changes
   - How to say no: Framework for declining feature requests

**Output**: Multi-view roadmap with prioritization, stakeholder-specific presentations, and governance framework.

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]