Product Planning Skill
Help with Product Owner and Business Analyst tasks using the product planning artifacts in this project.
Context Files
Before responding to product planning requests, read the relevant context files in product-planning/:
| File |
When to Read |
PRODUCT_VISION.md |
Always read first - provides product context |
personas/PERSONAS.md |
When writing user stories or considering user needs |
backlog/BACKLOG.md |
When prioritizing, planning sprints, or checking existing work |
roadmap/ROADMAP.md |
When discussing timelines or release planning |
Templates
Use templates from product-planning/templates/ when creating new artifacts:
USER_STORY_TEMPLATE.md - For new user storiesEPIC_TEMPLATE.md - For new epicsPRD_TEMPLATE.md - For product requirement documentsSPRINT_PLANNING_TEMPLATE.md - For sprint planning
Common Tasks
Writing User Stories
- Read
PRODUCT_VISION.md and personas/PERSONAS.md
- Use the user story format: "As a [persona], I want [goal], so that [benefit]"
- Include 3-5 acceptance criteria in Given/When/Then format
- Reference which persona benefits most
- Suggest story points (1, 2, 3, 5, 8, 13)
Prioritizing Backlog
- Read
backlog/BACKLOG.md to see current items
- Apply RICE scoring:
- Reach: How many users impacted?
- Impact: How much value? (3=massive, 2=high, 1=medium, 0.5=low)
- Confidence: How certain? (100%, 80%, 50%)
- Effort: Person-weeks of work
- Score = (Reach × Impact × Confidence) / Effort
- Provide reasoning for priority order
Sprint Planning
- Review backlog and identify ready items
- Consider team capacity (story points)
- Identify dependencies between items
- Create a cohesive sprint goal
- Balance feature work with tech debt
Creating PRDs
- Read product vision for alignment
- Use
PRD_TEMPLATE.md structure
- Include measurable success metrics
- Document edge cases and error handling
- List dependencies and risks
Best Practices
- Always reference personas by name (e.g., "Casual Carl", "Serious Sarah")
- Use INVEST criteria for stories: Independent, Negotiable, Valuable, Estimable, Small, Testable
- Keep acceptance criteria specific and testable
- Consider offline/PWA requirements for this app
- Reference accessibility requirements
Updating Artifacts
When creating new stories, epics, or other artifacts:
- Add them to the appropriate file in
product-planning/
- Update
backlog/BACKLOG.md with new items
- Maintain consistent ID numbering (US-XXX, E-XXX)
1---2name: product-planning3description: Product Owner / Business Analyst toolkit for product planning tasks. Use when the user wants to: - Write or refine user stories, epics, or acceptance criteria - Create or review PRDs (Product Requirement Documents) - Prioritize backlog items (RICE scoring, MoSCoW, etc.) - Plan sprints or releases - Create or update product roadmaps - Conduct competitive analysis or user research - Write release notes or stakeholder updates MANDATORY TRIGGERS: user story, epic, PRD, backlog, sprint planning, roadmap, acceptance criteria, product requirements, prioritize, story points, PO, BA, product owner, business analyst4---5
6# Product Planning Skill
7
8Help with Product Owner and Business Analyst tasks using the product planning artifacts in this project.
9
10## Context Files
11
12Before responding to product planning requests, read the relevant context files in `product-planning/`:
13
14| File | When to Read |
15|------|--------------|
16| `PRODUCT_VISION.md` | Always read first - provides product context |
17| `personas/PERSONAS.md` | When writing user stories or considering user needs |
18| `backlog/BACKLOG.md` | When prioritizing, planning sprints, or checking existing work |
19| `roadmap/ROADMAP.md` | When discussing timelines or release planning |
20
21## Templates
22
23Use templates from `product-planning/templates/` when creating new artifacts:
24
25- `USER_STORY_TEMPLATE.md` - For new user stories
26- `EPIC_TEMPLATE.md` - For new epics
27- `PRD_TEMPLATE.md` - For product requirement documents
28- `SPRINT_PLANNING_TEMPLATE.md` - For sprint planning
29
30## Common Tasks
31
32### Writing User Stories
33
341. Read `PRODUCT_VISION.md` and `personas/PERSONAS.md`
352. Use the user story format: "As a [persona], I want [goal], so that [benefit]"
363. Include 3-5 acceptance criteria in Given/When/Then format
374. Reference which persona benefits most
385. Suggest story points (1, 2, 3, 5, 8, 13)
39
40### Prioritizing Backlog
41
421. Read `backlog/BACKLOG.md` to see current items
432. Apply RICE scoring:
44 - **R**each: How many users impacted?
45 - **I**mpact: How much value? (3=massive, 2=high, 1=medium, 0.5=low)
46 - **C**onfidence: How certain? (100%, 80%, 50%)
47 - **E**ffort: Person-weeks of work
483. Score = (Reach × Impact × Confidence) / Effort
494. Provide reasoning for priority order
50
51### Sprint Planning
52
531. Review backlog and identify ready items
542. Consider team capacity (story points)
553. Identify dependencies between items
564. Create a cohesive sprint goal
575. Balance feature work with tech debt
58
59### Creating PRDs
60
611. Read product vision for alignment
622. Use `PRD_TEMPLATE.md` structure
633. Include measurable success metrics
644. Document edge cases and error handling
655. List dependencies and risks
66
67## Best Practices
68
69- Always reference personas by name (e.g., "Casual Carl", "Serious Sarah")
70- Use INVEST criteria for stories: Independent, Negotiable, Valuable, Estimable, Small, Testable
71- Keep acceptance criteria specific and testable
72- Consider offline/PWA requirements for this app
73- Reference accessibility requirements
74
75## Updating Artifacts
76
77When creating new stories, epics, or other artifacts:
781. Add them to the appropriate file in `product-planning/`
792. Update `backlog/BACKLOG.md` with new items
803. Maintain consistent ID numbering (US-XXX, E-XXX)
majiayu000