Product
Specs, roadmaps, user research synthesis, stakeholder updates, competitive scans.
PMs juggle synthesis: turning interviews into specs, backlog into roadmap, telemetry into stories. The mechanical part of that work is where Pace earns its keep. Run /product-management:synthesize on a stack of interview transcripts and reclaim a day of your week.
Plugins to install
Pick from this set for the role. Primary plugins are essential; companions multiply value.
- product-management primary
Specs, roadmaps, user research synthesis, stakeholder updates, competitive scans.
claude plugin install product-management@pace - design companion
Research synthesis and dev-handoff conversations live across the seam.
claude plugin install design@pace - data companion
Roadmap prioritization grounded in actual usage data.
claude plugin install data@pace - engineering companion
Spec ↔ scope conversations are smoother when both sides see the same context.
claude plugin install engineering@pace
Connectors to set up
Claude prompts to authorize each one the first time a relevant skill fires. You only do this once per project.
- Linear
- Asana
- Monday
- ClickUp
- Jira
- Notion
- Figma
- Amplitude
- Pendo
- Intercom
- Fireflies
Workflows
Common ways teams use these plugins day to day. Each one is a starting point; adapt the prompt to your context.
-
Feature spec
Writes a spec from a one-liner: user story, requirements, scope cuts, success metrics, edge cases.
/product-management:spec for cohort filtering in the analytics dashboard -
Roadmap from backlog
Reads Linear/Jira backlog and shapes a quarter or half. Highlights dependencies and parking-lot items.
/product-management:roadmap Q1 from current Linear backlog -
User research synthesis
Reads transcripts, surfaces patterns, names themes, generates a research summary doc.
/product-management:synthesize these 12 user interview transcripts -
Stakeholder update
Drafts the biweekly or monthly update: what shipped, what slipped, what is next, asks.
/product-management:update biweekly to exec team -
Competitive landscape scan
Pulls competitor product updates from the last week or quarter and writes a brief on what is shipping, what is shifting.
/product-management:competitive scan our space this week
Tips & tricks
Field-tested patterns from teams that have already shipped a quarter or two on these plugins.
-
Synthesize is the killer skill
/product-management:synthesize on raw interview transcripts saves a full day every week. Connect Fireflies so transcripts arrive automatically.
-
Ground roadmaps in data
Pair /product-management:roadmap with /data:* so prioritization argues from real usage, not vibes.
-
Spec quality compounds
A spec that is clear, scoped, and has metrics defined upfront saves multiple weeks of re-scoping later. Invest the hour with /product-management:spec.
-
Use it for retros too
/product-management:synthesize works on retro notes the same way it works on interviews. Pattern-find what teams keep saying.
-
Stakeholder cadence beats one-offs
Run /product-management:update on a fixed schedule (biweekly) rather than reactively. Trust compounds with consistency.
-
Competitive scans weekly
/product-management:competitive once a week is enough; daily is noise.