clawdbot_pm_use_cases.md
Clawdbot use cases for Product Managers
High-leverage ways to use Clawdbot as a PM: turning messy inputs into crisp decisions + artifacts.
1) PRD co-writer + spec clarifier
Input: goal, user/persona, constraints, success metrics.
Output: PRD + edge cases + out-of-scope + open questions.
Best practice: require:
- “What would make this fail?” section
- explicit assumptions list
2) Meeting → decisions & next actions
Input: messy notes or transcript.
Output:
- decisions
- action items (owner/date)
- risks
- 5-line recap you can forward
Tip: ask it to flag unresolved disagreements explicitly.
3) Roadmap pressure test
Input: quarterly goals + candidate initiatives.
Output: priority stack with rationale, sequencing, dependencies, and a “what we’re not doing” narrative.
4) Customer feedback clustering
Input: 20–200 snippets (tickets, sales notes, tweets).
Output: clusters/themes, jobs-to-be-done labels, 3–5 roadmap bets, and “evidence quotes” per bet.
5) Competitive teardown (fast)
Input: competitor + 3 links/screenshots.
Output: positioning, core loops, pricing, moats, who it’s for, and response options (build/partner/ignore).
6) Release comms pack (one go)
Input: changelog + target persona.
Output: announcement post, email, help-center draft, sales enablement bullets, and “what to screenshot” guidance.
7) Spec-to-tasks for eng/design
Input: PRD or Figma link.
Output: implementation plan, API changes, analytics/events, rollout plan, and QA checklist.
Next step: tell Viper what type of PM work you do (0–1 growth, B2B platform, consumer, internal tools), and we’ll turn the top 3 into reusable templates.