Pace
All teams / Product

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 `synthesize` on a stack of interview transcripts and reclaim a day of your week.

Install for Product

The full product starter set is 4 plugins. Pick the install path that matches you.

Cowork (no terminal)

Click each link below; Cowork opens and asks you to confirm. Restart Cowork after the last one so connectors register.

  1. 1 Install product-management
  2. 2 Install design
  3. 3 Install data
  4. 4 Install engineering
After the last install, restart Cowork. The MCP servers (Slack, HubSpot, etc.) only register cleanly on a fresh app start. Quit the app fully, then reopen it.

Terminal (one command)

If you have claude on your PATH already, this installs the whole set in one go.

npx pace-tools install product-management design data engineering

pace-tools wraps claude plugin install; runs claude plugin marketplace add GoldenBerry-SO/Pace automatically if you haven't registered the marketplace yet.

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.

    Spec cohort filtering for the analytics dashboard.

  • Roadmap from backlog

    Reads Linear/Jira backlog and shapes a quarter or half. Highlights dependencies and parking-lot items.

    Build a Q1 roadmap from the current Linear backlog.

  • User research synthesis

    Reads transcripts, surfaces patterns, names themes, generates a research summary doc.

    Synthesize these 12 user interview transcripts. Themes, surprises, follow-up questions.

  • Stakeholder update

    Drafts the biweekly or monthly update: what shipped, what slipped, what is next, asks.

    Write the biweekly product update for the 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.

    Scan our space this week. Launches, fundraises, repositioning. What we should react to.

Just say it

You don't have to memorize slash commands. After installing, type natural sentences into Claude and the right skill will fire. Each row is a real example.

  • You say

    Synthesize these 8 user interviews into themes

    Claude triggers synthesize-research
  • You say

    Write a PRD for the new collaboration feature

    Claude triggers write-spec
  • You say

    Update stakeholders on this sprint's progress

    Claude triggers stakeholder-update
  • You say

    What did our competitors ship this week?

    Claude triggers competitive-brief
  • You say

    Brainstorm 10 ways to improve onboarding

    Claude triggers product-brainstorming
  • You say

    Plan next sprint based on this backlog

    Claude triggers sprint-planning

Tips & tricks

Field-tested patterns from teams that have already shipped a quarter or two on these plugins.

  • Synthesize is the killer skill

    `synthesize` on raw interview transcripts saves a full day every week. Connect Fireflies so transcripts arrive automatically.

  • Ground roadmaps in data

    Pair `roadmap` with the data plugin 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 `spec`.

  • Use it for retros too

    `synthesize` works on retro notes the same way it works on interviews. Pattern-find what teams keep saying.

  • Stakeholder cadence beats one-offs

    Run `update` on a fixed schedule (biweekly) rather than reactively. Trust compounds with consistency.

  • Competitive scans weekly

    `competitive` once a week is enough; daily is noise.

See also