From role-pm
Draft a product spec (PRD) for a feature or initiative, pulling context from Notion, Slack, and Drive first so the draft isn't starting from zero. Produces a draft — does not publish to Notion without approval.
npx claudepluginhub sitloboi2012/team-marketplace --plugin role-pmThis skill uses the workspace's default tool permissions.
**Invocation: user only.** Drafts a spec; saves to Notion only after explicit approval.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Share bugs, ideas, or general feedback.
Invocation: user only. Drafts a spec; saves to Notion only after explicit approval.
From $ARGUMENTS, identify:
If the ask is vague ("do something about onboarding"), ask 1-2 clarifying questions — don't guess the problem.
Report what you found before drafting. The user should be able to say "use the Sept 14 thread, ignore the rest."
Use this template. Fill what you have; mark gaps clearly with [NEEDS INPUT: ...].
# <Feature name>
**TL;DR** <one sentence. What and why.>
**Status:** draft · **Owner:** <user> · **Date:** <today>
## Problem
<2-3 paragraphs. Who has the problem, how often, what's the cost of not solving.>
## Users
<Specific segment(s). Numbers if we have them.>
## Goals
- <primary outcome — measurable if possible>
- <secondary>
## Non-goals
- <what this explicitly does not do — prevents scope creep>
## Proposed solution
<What we're going to build. Lead with user-facing behavior, not implementation.>
## Open questions
- [ ] <question> — needs input from <eng | design | legal | ...>
- [ ] ...
## Risks
- <risk>: <mitigation or "accepted">
## Rollout
<How we'll ship — behind a flag? staged rollout? internal first?>
## Metrics
- Primary: <metric + target + timeline>
- Secondary: <metric>
## Appendix — context we pulled
- <Slack link>: <one line>
- <Notion link>: <one line>
Show the draft. Ask:
[NEEDS INPUT] the user can resolve right now?On "ship it" / "publish" / equivalent:
/team-core:draft-email-style flow — draft first, send on approval).[NEEDS INPUT: current baseline].