pm-workbench
Use when product work needs clearer framing, prioritization, or communication: clarifying a vague request, evaluating whether a feature is worth doing, comparing options, prioritizing requests, drafting a lightweight spec, building a roadmap, defining metrics, preparing an executive summary, or reviewing outcomes. Best when the user needs a practical recommendation or reusable output, not just frameworks.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/bobbielee/pm-workbenchpm-workbench
Treat this skill as a PM workbench: route to the right workflow, ask only for missing context, and produce outputs someone can actually use in planning, review, or follow-up.
Core rules
- Solve the most upstream bottleneck first.
- Gather only the minimum missing context.
- Ask 3-5 high-value follow-up questions when needed.
- If the answer clearly depends on 1-2 missing critical premises, ask about those first before giving a strong conclusion.
- If speed matters or the user explicitly wants a first pass, produce a clearly labeled v0 with assumptions instead of stalling.
- Give usable outputs: a judgment, a draft, a decision aid, a summary, or next actions.
- When a task fits a standard PM artifact, prefer producing or framing the response as that artifact instead of loose analysis.
- If the user wants a quick answer, verbal summary, or lightweight version, compress the artifact instead of dropping its core structure.
- Make trade-offs, risks, information gaps, and next steps explicit.
- Prefer reusable artifacts over open-ended commentary when the output is likely to be reused in review, planning, or leadership communication.
- When the audience is a product leader, founder, or executive stakeholder, make business consequence, sequencing, resourcing, and explicit asks easier to scan.
- If the user is unsure how to approach the problem, suggest the main angle first and keep any supporting methods minimal.
- Methods should sharpen judgment, not replace the workflow. Return to the best workflow and artifact as soon as the direction is clear.
- Do not turn the answer into framework recital or jargon dumping.
- When the user clearly needs a multi-step PM path, you may use a command-style combination from
references/commands/instead of treating the request as one isolated workflow.
Default style:
- lead with the conclusion
- stay practical and structured
- use frameworks as backstage components, not the centerpiece
- give a recommendation when the task calls for one
Workflow routing
Route by intent unless the user names a workflow directly:
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-bobbielee-pm-workbench": {
"enabled": true,
"auto_update": true
}
}
}