pm-workbench

Clarifies vague product requests into decision-ready recommendations and reusable PM artifacts.

33|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/BobbieLee/pm-workbench --skill pm-workbench
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-workbench
Source: https://github.com/BobbieLee/pm-workbench/tree/main
Command: npx skills add https://github.com/BobbieLee/pm-workbench --skill pm-workbench

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

pm-workbench helps product people turn vague, politically loaded, or under-specified requests into clear decisions, reusable artifacts, and next moves they can defend.

Core Features & Use Cases

  • Clarifies fuzzy product asks before solutioning starts.
  • Evaluates feature value, compares options, and prioritizes competing work with explicit trade-offs.
  • Drafts lightweight PM artifacts such as decision briefs, roadmaps, metrics scorecards, exec summaries, postmortems, and founder or product-leader reviews.
  • Supports command-style multi-step PM work when a single workflow is not enough.
  • Use it when a boss gives a vague direction, a team is arguing about roadmap slots, leadership needs a one-page update, or a founder needs a sharper product and business call.

Quick Start

Ask pm-workbench to turn a real vague product request into a clear problem statement, a recommendation, or a reusable PM artifact.

Frequently Asked Questions about pm-workbench

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn vague product requests into decision-ready recommendations?

Transforming vague product requests into decision-ready recommendations requires clarifying the under-specified ask, evaluating feature value, and framing explicit trade-offs. This process converts ambiguous directions into defensible problem statements and actionable next moves.

What is the best way to prioritize competing roadmap slots with explicit trade-offs?

Prioritizing competing roadmap slots with explicit trade-offs involves comparing feature options against capacity constraints and business value. This yields a defensible roadmap plan that resolves team arguments through clear product-leader trade-off calls.

How do I draft a lightweight executive summary for a product decision?

Drafting a lightweight executive summary for a product decision involves synthesizing the recommendation, key metrics, and trade-offs into a one-page update. This format gives leadership the necessary context to approve or adjust the product direction.

When do I need a structured postmortem for product management?

You need a structured postmortem for product management when a feature launches or fails and you must document what happened. It clarifies the timeline, extracts reusable insights, and turns subjective team reflections into objective artifacts.

Does this approach support founder trade-off calls under capacity constraints?

Yes, this approach supports founder trade-off calls under capacity constraints by routing multi-step PM workflows to compare options. It delivers leader-grade outputs that clarify uncertainty and help founders make sharper product and business decisions.