PM Master Product Management Workflow

Problem it solves

Product managers often get stuck when context is incomplete, goals are fuzzy, and artifacts are not review-ready. A PRD may describe background but miss error flows, a roadmap may list features without trade-offs, and a launch review may lack observable evidence. PM Master turns these tasks into decision-ready outputs: engineering-review PRDs, user stories, demand evaluation, prioritization, metric design, and launch reviews.

How it works

It runs as a single skill with internal routing. After identifying the task type, it reads only the relevant workflows/, templates/, and references/ modules instead of dumping methodology at once. The core loop starts from the north-star goal, non-goals, and success evidence; separates facts, assumptions, and judgments; and produces scope, main flows, edge cases, permissions, metrics, acceptance criteria, and risks. If input is incomplete, it provides a usable draft marked as assumption-based, then lists the questions that need confirmation. Formal PRDs default to an engineering-review standard, covering state machines, tracking fields, API or config suggestions, fallbacks, and acceptance cases.

Boundaries

It fits product documentation, demand evaluation, strategy analysis, metrics design, and review communication. It is not intended for marketing copy, legal compliance, code fixes, visual design, or simple definition questions. For high-risk decisions, treat its risk levels, validation plan, and rollback guidance as a structured input, not a final conclusion.