Product Manager Toolkit
Install this when you need stakeholder-ready PRD sections—problem, market, solution, and scope—before committing engineering time as a solo builder.
Overview
Product Manager Toolkit is an agent skill most often used in Validate (also Idea, Build) that generates structured PRD sections—executive summary, problem, market case, and scoped solution—for solo builders defining what
Install
npx skills add https://github.com/davila7/claude-code-templates --skill product-manager-toolkitWhat is this skill?
- Standard PRD template spanning executive summary, problem definition, and solution overview
- Executive summary block with problem, solution, business impact, timeline, resources, and 3–5 KPI slots
- Customer problem framing (who/what/when/where/why/impact) plus TAM, SAM, SOM market opportunity
- Solution overview with user journey, differentiation, prioritized in-scope features, and explicit out-of-scope boundarie
- Business case section covering revenue, cost savings, strategic value, and risk if you skip the work
- Executive summary template lists 6 components: problem, solution, business impact, timeline, resources, and success metr
- Problem definition spans 3 areas: customer problem, market opportunity, and business case
- Solution overview includes in-scope features, out-of-scope boundaries, and user journey
Adoption & trust: 540 installs on skills.sh; 27.8k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know what you want to build loosely but lack a disciplined PRD that ties customer pain, market context, and feature scope to measurable outcomes.
Who is it for?
Solo founders and indie hackers who need a full PRD skeleton before MVP build, investor updates, or agent-driven implementation plans.
Skip if: Teams that already maintain an approved spec in Notion/Jira with no need to regenerate PRD structure, or tasks that only need a single bugfix ticket without product framing.
When should I use this skill?
When you need to draft or complete a Product Requirements Document, executive summary, or scoped feature spec for stakeholders or your coding agent.
What do I get? / Deliverables
You leave with a Standard PRD outline—executive summary, problem and market chapters, and in/out-of-scope solution—that you can approve and hand to implementation or agent planning skills.
- Standard PRD markdown structure with executive summary
- Problem definition covering customer, market, and business case
- Solution overview with prioritized in-scope features and explicit out-of-scope list
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
PRDs are the canonical artifact for locking what to build after discovery; Prism shelves product-spec skills on Validate where scope is decided before full Build execution. The readme is a Standard PRD Template for in/out-of-scope features, success metrics, and business case—exactly the scope-definition work in validate, not day-to-day coding.
Where it fits
Turn landing-page learnings into a PRD with KPIs and explicit out-of-scope list before coding the MVP.
Capture TAM/SAM/SOM and competition gaps in the market-opportunity section after discovery interviews.
Refresh in-scope feature priorities and user journey in the solution chapter before an agent implements the next milestone.
Reuse executive-summary success metrics to align launch checklist acceptance criteria with what you committed in the PRD.
How it compares
Use structured PRD templates instead of dumping unstructured feature lists into chat when scoping a product.
Common Questions / FAQ
Who is product-manager-toolkit for?
It is for solo and indie builders who wear the PM hat and need PRD-ready sections without a dedicated product team or PM coach in the loop.
When should I use product-manager-toolkit?
Use it in Validate to lock MVP scope and success metrics, in Idea to document market opportunity after competitor research, and in Build when refreshing in-scope features before a major agent coding push.
Is product-manager-toolkit safe to install?
Treat it as documentation templates; review the Security Audits panel on this Prism page and the upstream repo before trusting any bundled scripts or non-template files in the full package.
SKILL.md
READMESKILL.md - Product Manager Toolkit
# Product Requirements Document (PRD) Templates ## Standard PRD Template ### 1. Executive Summary **Purpose**: One-page overview for executives and stakeholders #### Components: - **Problem Statement** (2-3 sentences) - **Proposed Solution** (2-3 sentences) - **Business Impact** (3 bullet points) - **Timeline** (High-level milestones) - **Resources Required** (Team size and budget) - **Success Metrics** (3-5 KPIs) ### 2. Problem Definition #### 2.1 Customer Problem - **Who**: Target user persona(s) - **What**: Specific problem or need - **When**: Context and frequency - **Where**: Environment and touchpoints - **Why**: Root cause analysis - **Impact**: Cost of not solving #### 2.2 Market Opportunity - **Market Size**: TAM, SAM, SOM - **Growth Rate**: Annual growth percentage - **Competition**: Current solutions and gaps - **Timing**: Why now? #### 2.3 Business Case - **Revenue Potential**: Projected impact - **Cost Savings**: Efficiency gains - **Strategic Value**: Alignment with company goals - **Risk Assessment**: What if we don't do this? ### 3. Solution Overview #### 3.1 Proposed Solution - **High-Level Description**: What we're building - **Key Capabilities**: Core functionality - **User Journey**: End-to-end flow - **Differentiation**: Unique value proposition #### 3.2 In Scope - Feature 1: Description and priority - Feature 2: Description and priority - Feature 3: Description and priority #### 3.3 Out of Scope - Explicitly what we're NOT doing - Future considerations - Dependencies on other teams #### 3.4 MVP Definition - **Core Features**: Minimum viable feature set - **Success Criteria**: Definition of "working" - **Timeline**: MVP delivery date - **Learning Goals**: What we want to validate ### 4. User Stories & Requirements #### 4.1 User Stories ``` As a [persona] I want to [action] So that [outcome/benefit] Acceptance Criteria: - [ ] Criterion 1 - [ ] Criterion 2 - [ ] Criterion 3 ``` #### 4.2 Functional Requirements | ID | Requirement | Priority | Notes | |----|------------|----------|-------| | FR1 | User can... | P0 | Critical for MVP | | FR2 | System should... | P1 | Important | | FR3 | Feature must... | P2 | Nice to have | #### 4.3 Non-Functional Requirements - **Performance**: Response times, throughput - **Scalability**: User/data growth targets - **Security**: Authentication, authorization, data protection - **Reliability**: Uptime targets, error rates - **Usability**: Accessibility standards, device support - **Compliance**: Regulatory requirements ### 5. Design & User Experience #### 5.1 Design Principles - Principle 1: Description - Principle 2: Description - Principle 3: Description #### 5.2 Wireframes/Mockups - Link to Figma/Sketch files - Key screens and flows - Interaction patterns #### 5.3 Information Architecture - Navigation structure - Data organization - Content hierarchy ### 6. Technical Specifications #### 6.1 Architecture Overview - System architecture diagram - Technology stack - Integration points - Data flow #### 6.2 API Design - Endpoints and methods - Request/response formats - Authentication approach - Rate limiting #### 6.3 Database Design - Data model - Key entities and relationships - Migration strategy #### 6.4 Security Considerations - Authentication method - Authorization model - Data encryption - PII handling ### 7. Go-to-Market Strategy #### 7.1 Launch Plan - **Soft Launch**: Beta users, timeline - **Full Launch**: All users, timeline - **Marketing**: Campaigns and channels - **Support**: Documentation and training #### 7.2 Pricing Strategy - Pricing model - Competitive analysis - Value proposition #### 7.3 Success Metrics | Metric | Target | Measurement Method | |--------|--------|-------------------| | Adoption Rate | X% | Daily Active Users | | User Satisfaction | X/10 | NPS Score | | Revenue Impact | $X | Monthly Recurring Revenue | | Performance | <Xms | P95 Response Time | ### 8. Risks & Mitigations | Risk | Probability | Impact | Mitigation