Product Manager

Problem Addressed

Product work often drifts when requirements, priorities, and delivery boundaries are not tied to a clear problem statement. Product Manager gives product owners and cross-functional teams a structured frame for strategy, roadmaps, PRDs, user stories, and backlog prioritization. It is especially useful before concept validation, release planning, or cross-team review, when scattered ideas need to become trackable product work items, and it helps the team identify which assumptions need validation and which requirements should be deferred.

How It Works

The skill organizes product decisions into repeatable workflows:
- PRD creation: from problem statement, target users, proposed solution, and success metrics to must-have / nice-to-have requirements, constraints, and dependencies.
- Feature prioritization: estimate Reach, Impact, Confidence, and Effort using RICE, then rank options and discuss trade-offs with stakeholders.
- User stories: write stories as As a [user], I want [goal] so that [benefit], add acceptance criteria, edge cases, and complexity estimates with the team.
- Boundary checks: route architecture, project tracking, user research, and market research to the appropriate specialized workflows rather than handling them here.

Boundaries and Notes

It fits product planning, roadmap work, PRD writing, backlog prioritization, and launch preparation. It should not replace engineering architecture decisions or project execution tracking. Use it to avoid solution-first thinking and vague requirements, define measurable outcomes, and pull in engineering early enough to assess feasibility.