Product Manager Assistant

Problem It Addresses

A product-management skill is not a substitute for engineering architecture; it clarifies what to build, why, and in what order. Use it when requirements are fuzzy, the backlog is crowded, or cross-functional discussions lack a shared frame: it structures product strategy, roadmaps, PRDs, user stories, feature prioritization, and launch planning to reduce rework caused by solution-first thinking, missing metrics, or engineering ambiguity.

How It Works

The skill organizes product decisions and documentation workflows:
- Product strategy and PRDs: starts with the problem statement, target users, proposed solution, success metrics, requirements, constraints, and dependencies, producing a reviewable product document.
- Feature prioritization: applies a RICE-style approach, estimating Reach, Impact, Confidence, and Effort, then ranking options so “everything is urgent” becomes a trade-off conversation.
- User stories and acceptance criteria: uses the “As a [user], I want [goal] so that [benefit]” pattern, then adds edge cases, complexity, and engineering estimates.
- Cross-functional coordination: supports product launch planning, competitive analysis, and build vs buy decisions with structured discussion material.

Boundaries And Notes

It is best for product-management process and decision support, not for technical architecture, project execution tracking, user-research methodology, or deep market research. For those areas, pair it with the corresponding skills, such as /solution-architect, /project-manager, /ux-researcher, or /market-researcher. Keep decisions anchored to measurable outcomes, and treat the generated workflow as a discussion artifact rather than final strategy; key assumptions still need validation against user and market evidence.