product-planning
12
总安装量
10
周安装量
#25812
全站排名
安装命令
npx skills add https://github.com/alexanderop/workouttracker --skill product-planning
Agent 安装分布
claude-code
7
opencode
7
gemini-cli
5
windsurf
4
codex
4
Skill 文档
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.mdandpersonas/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.mdto 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.mdstructure - 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.mdwith new items - Maintain consistent ID numbering (US-XXX, E-XXX)