Product Management (Specs, Roadmaps, Research)
Feature specs and PRDs, roadmap planning, stakeholder updates, user research synthesis, competitive analysis, and metrics review for PMs.
Before & after
Same prompt, same agent — the only difference is the skill.
A PRD is a great way to clarify requirements before building. Writing a good one involves understanding the problem you're solving, who needs it, and how you'll measure success. To create a PRD that the engineering team will actually follow, I'd need to understand your product better. What's the core use case for this chatbot? Who are the users, and what problems does it solve? Are there competitive chatbots out there doing something similar? How will this fit into your existing product? I can help you structure a PRD with sections for requirements, success metrics, and user stories, but the specific content really depends on your business goals and constraints. Maybe we could start with a problem statement?
PRD: AI-Powered Customer Support Chatbot
OBJECTIVE: Reduce support queue time by 40% and improve CSAT from 78% to 85% in 90 days
PROBLEM STATEMENT:
Customer support receives 300+ queries daily; 60% are repetitive questions (password reset, billing, how-to). Current response time: 4-8 hours. Support team burned out. Solution: Chatbot handles Tier-1 questions, escalates complex issues to humans.
USER STORIES:
US-1: Customer asks FAQ question
AS A customer
I WANT to get an immediate answer
SO THAT I don't wait for support team
ACCEPTANCE CRITERIA:
→ Chatbot responds within 2 seconds
→ Answer matches knowledge base (100% accuracy required)
→ User can escalate to human with one click
→ Interaction logged for training
US-2: Support agent reviews escalated tickets
AS A support agent
I WANT to see chatbot conversation history
SO THAT I don't repeat information
ACCEPTANCE CRITERIA:
→ Full chat transcript visible in ticket view
→ Questions already asked by chatbot highlighted
→ Escalation reason ("I don't understand") shown
US-3: Manager monitors chatbot performance
AS A support manager
I WANT a dashboard showing resolution rate by category
SO THAT I can identify gaps in knowledge base
ACCEPTANCE CRITERIA:
→ Daily/weekly resolution rate (goal: 65%)
→ False answer rate tracked (goal: <2%)
→ CSAT for chatbot-handled cases measured separately
→ Alert if escalation rate exceeds 40%
SCOPE:
IN (90-day MVP):
→ Password reset, billing, how-to categories (350 questions)
→ Text-only (no voice, no video)
→ Integration with Zendesk (escalations auto-create tickets)
→ Admin dashboard for knowledge base updates
OUT (Future phase):
→ Sentiment analysis
→ Multi-language support
→ Voice/video support
→ Predictive escalation
SUCCESS METRICS:
→ Resolution rate: 65% (measured: "did customer close ticket without agent response")
→ CSAT improvement: 78% → 85%
→ Response time: <2 seconds
→ False answer rate: <2%
→ Adoption: 60% of new customer inquiries hit chatbot
→ Support time saved: 20 hours/week
RISKS & MITIGATION:
→ Risk: Chatbot gives wrong answer → Mitigation: 2-week human review of all responses before launch
→ Risk: Support team resists (fear of layoffs) → Mitigation: Redeploy team to higher-value work (custom issues)
→ Risk: Low adoption → Mitigation: Add positive feedback loop ("thanks for rating this helpful")
TIMELINE:
Week 1-2: Collect FAQ data, train model, build admin UI
Week 3-4: Human review, Zendesk integration, team training
Week 5-6: Phased rollout (10% of traffic, monitor)
Week 7-12: Full launch, monitoring, iteration
DEPENDENCIES:
→ Zendesk API access (dev team)
→ QA for edge cases (support team, 20 hours)
→ Marketing for launch comms (1 week notice)
OWNER: Product Manager (Alice)
ENG LEAD: Backend engineer (Bob)
APPROVED: CTO, VP SupportAbout this skill
name: kw-product-management description: Use when feature specs and PRDs, roadmap planning, stakeholder updates, user research synthesis, competitive analysis, and metrics review for PMs.
Product Management (Specs, Roadmaps, Research)
Anthropic's Product Management plugin covers the PM workflow end to end. /write-spec generates a structured PRD (user stories, requirements prioritization, success metrics, scope) from a problem statement. /roadmap-update creates or reprioritizes roadmaps in Now/Next/Later, quarterly-themes, or OKR-aligned formats with dependency mapping. /stakeholder-update generates audience-tailored status updates. /synthesize-research turns interview notes, survey data, and support tickets into themes, personas, and opportunity areas. Frameworks like How Might We, JTBD, First Principles, and Opportunity Solution Trees are baked into the brainstorming path.
What you get
- /write-spec command (structured PRD with user stories and success metrics)
- /roadmap-update command (Now/Next/Later, quarterly, OKR formats with dependencies)
- /stakeholder-update command (audience-tailored status)
- /synthesize-research command (themes, personas, opportunities)
- brainstorming with How Might We, JTBD, First Principles, Opportunity Solution Trees
- connectors for Slack, Linear, Asana, Monday, ClickUp, Jira, Notion, Figma, Amplitude, Pendo, Intercom, Fireflies
Customize your output
- Command: write-spec, roadmap-update, stakeholder-update, synthesize-research
- Roadmap format: Now/Next/Later, quarterly themes, OKR-aligned
- Audience: executives, engineering, customers
- Framework: HMW, JTBD, First Principles, OST
Example output
Given a problem statement and three customer interviews, /write-spec drafts a PRD with the target user, three prioritized requirements, two success metrics, and out-of-scope items called out.
Best for
PMs shipping specs, roadmaps, and stakeholder updates on Linear, Jira, or Asana
SKILL.md preview
---
name: kw-product-management
description: Use for end-to-end product management work: writing PRDs, building or reprioritizing roadmaps, drafting stakeholder updates, or synthesizing user research into themes and opportunities.
version: 1.0.0
category: Product
author: AgentVolt
license: proprietary
tags:
- product
- p3
---
# Product Management (Specs, Roadmaps, Research)
Covers the end-to-end PM workflow: writing structured PRDs, building or reprioritizing roadmaps, generating stakeholder updates, and synthesizing user research into themes and opportunities.
## When to use
… (sign up to view the full skill)