Product Manager Toolkit
Turn a vague product idea into an evidence-backed PRD with problem statement, prioritized user stories, solution overview, and success criteria before engineering starts.
Overview
Product Manager Toolkit is an agent skill most often used in Validate (also Build) that produces a full product requirements document from problem evidence through prioritized stories and solution overview.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill product-manager-toolkitWhat is this skill?
- PRD skeleton with document info, status, reviewers, and target release
- Problem block: who is affected, evidence links, cost of inaction
- User story table with Must Have / Should Have / Nice to Have priorities
- Solution overview with key user flows and mechanism explanation
- Success metrics section for measurable post-ship validation
- PRD sections include problem, user stories table, solution overview with 3 flow slots, and success criteria blocks
Adoption & trust: 800 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are ready to code but lack a single approved spec that ties user pain, scope priorities, and success metrics together.
Who is it for?
Indie PM-founder pairs who need a lightweight PRD before agent-driven implementation or a small release milestone.
Skip if: Pure engineering tasks with an already-approved spec, or deep technical architecture-only docs with no product narrative.
When should I use this skill?
User needs a PRD, product scope doc, user stories with priorities, or structured problem/solution write-up before implementation.
What do I get? / Deliverables
You get a draft-to-approved PRD with prioritized user stories and flows your agent can implement against in the Build phase.
- PRD markdown with metadata and status
- Prioritized user story table
- Solution overview and enumerated key user flows
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Scoping and approval happen in Validate when you still need a shared artifact to prove the idea is worth building. The toolkit is structured as a full PRD template—problem, users, solution, flows—exactly what you lock during scope validation.
Where it fits
Draft a PRD that ties interview quotes to Must Have stories before committing two weeks of build time.
Document key flows for a clickable prototype so agents implement the same journeys.
Update status to In Review and add success metrics before a beta cut.
Reference target release and reviewers in launch prep checklists derived from the approved PRD.
How it compares
Structured PRD template skill, not a codebase planner or ticket exporter.
Common Questions / FAQ
Who is product-manager-toolkit for?
Solo and indie builders acting as their own PM who want agent help drafting scope, stories, and success criteria in standard PRD form.
When should I use product-manager-toolkit?
In Validate when scoping an MVP or feature bet, and in Build when refreshing PM docs before a milestone—before you ask the agent to implement open-ended work.
Is product-manager-toolkit safe to install?
Check the Security Audits panel on this Prism page; the skill is document templates and does not imply elevated agent permissions.
SKILL.md
READMESKILL.md - Product Manager Toolkit
# Product Requirements Document (PRD) ## Document Info | Field | Value | |-------|-------| | **Author** | [Your Name] | | **Status** | Draft / In Review / Approved | | **Created** | YYYY-MM-DD | | **Last Updated** | YYYY-MM-DD | | **Reviewers** | [Names] | | **Target Release** | [Quarter or Date] | --- ## Problem Statement ### What problem are we solving? [Describe the user problem in 2-3 sentences. Focus on the pain, not the solution.] ### Who is affected? [Identify the user segment(s) experiencing this problem.] ### How do we know this is a problem? [Link to evidence: interview insights, support tickets, analytics data, churn analysis.] ### What happens if we do nothing? [Quantify the cost of inaction: lost revenue, churn risk, competitive disadvantage.] --- ## User Stories | # | As a... | I want to... | So that... | Priority | |---|---------|-------------|-----------|----------| | 1 | [role] | [capability] | [benefit] | Must Have | | 2 | [role] | [capability] | [benefit] | Should Have | | 3 | [role] | [capability] | [benefit] | Nice to Have | --- ## Solution Overview ### Proposed Solution [High-level description of what we will build. 3-5 sentences.] ### Key User Flows [Describe the primary user interactions. Include wireframes or mockups if available.] 1. **Flow 1:** [Description] 2. **Flow 2:** [Description] 3. **Flow 3:** [Description] ### How It Works [Explain the mechanism or approach. Include technical considerations if relevant.] --- ## Success Metrics | Metric | Current | Target | Timeframe | |--------|---------|--------|-----------| | [Primary metric] | [Baseline] | [Goal] | [When] | | [Secondary metric] | [Baseline] | [Goal] | [When] | | [Guardrail metric] | [Baseline] | [Must not worsen] | [When] | ### How We Will Measure [Describe tracking approach: analytics events, surveys, A/B test design.] --- ## Technical Requirements ### System Requirements - [Requirement 1: e.g., API response time < 200ms] - [Requirement 2: e.g., Support 10K concurrent users] - [Requirement 3: e.g., Mobile responsive] ### Dependencies - [Dependency 1: e.g., Payment service API update] - [Dependency 2: e.g., Design system component] ### Security & Privacy - [Data handling requirements] - [Authentication/authorization needs] - [Compliance considerations] --- ## Timeline | Phase | Dates | Deliverables | |-------|-------|-------------| | Design | [Start - End] | Wireframes, user flows, design specs | | Development | [Start - End] | Feature implementation, unit tests | | QA | [Start - End] | Test plan execution, bug fixes | | Beta | [Start - End] | Limited rollout, feedback collection | | GA | [Date] | Full release, documentation, training | --- ## Risks | Risk | Likelihood | Impact | Mitigation | |------|-----------|--------|-----------| | [Risk 1] | High/Med/Low | High/Med/Low | [Plan] | | [Risk 2] | High/Med/Low | High/Med/Low | [Plan] | --- ## Out of Scope The following items are explicitly NOT included in this release: - [Item 1: brief explanation of why] - [Item 2: brief explanation of why] - [Item 3: brief explanation of why] --- ## Decision Log | # | Decision | Date | Decided By | Rationale | |---|----------|------|-----------|-----------| | 1 | [Decision] | [Date] | [Name] | [Why] | --- ## Change History | Version | Date | Author | Changes | |---------|------|--------|---------| | 0.1 | [Date] | [Name] | Initial draft | feature,reach,impact,confidence,effort Example Feature 1,500,3,0.8,5 Example Feature 2,1000,2,0.9,3 Example Feature 3,300,1,1.0,2 # Product Management Frameworks Comprehensive reference for prioritization, discovery, and measurement frameworks. --- ## Table of Contents - [Prioritization Frameworks](#prioritization-frameworks) - [RICE Framework](#rice-framework) - [Value vs Effort Matrix](#value-vs-effort-matrix) - [MoSCoW Method](#moscow-method) - [ICE Scoring](#ice-scoring) - [Kano Model](#kano-model) - [Discovery Frameworks](#discovery-frameworks) - [Custom