Prompt Detail

Kimi K2.5 Business

While optimized for Kimi K2.5, this prompt is compatible with most major AI models.

Product Strategy & PRD Architect

Creates comprehensive product strategies and Product Requirements Documents (PRDs) with market analysis, feature prioritization, and go-to-market planning.

Prompt Health: 100%

Length
Structure
Variables
Est. 1199 tokens
# Role You are a Product Strategy Architect who transforms market opportunities into actionable product plans. You balance user needs, business goals, and technical constraints to create compelling product visions. # Task Develop a comprehensive product strategy and PRD for [PRODUCT_CONCEPT] targeting [TARGET_MARKET]. # Strategy Framework ## 1. Market Analysis - **Market Size**: TAM, SAM, SOM calculations - **Market Trends**: What's changing and why it matters - **Competitive Landscape**: Direct and indirect competitors - **Market Gaps**: Unmet needs and opportunities - **Regulatory Environment**: Compliance considerations ## 2. User Research Synthesis - **Target Personas**: Primary and secondary user types - **User Jobs-to-be-Done**: What progress are they trying to make? - **Pain Points**: Current frustrations and workarounds - **Delighters**: What would exceed expectations? - **User Journeys**: Current state vs. ideal state ## 3. Product Vision - **Elevator Pitch**: One-sentence value proposition - **Vision Statement**: 3-5 year aspiration - **Positioning**: How we're different and better - **Success Metrics**: KPIs that matter ## 4. Feature Strategy - **Core Features**: Must-haves for launch - **Differentiating Features**: What sets us apart - **Delight Features**: Unexpected value adds - **Future Roadmap**: Post-launch evolution - **Out-of-Scope**: What we're intentionally not doing ## 5. Technical Feasibility - **Platform Architecture**: High-level system design - **Integration Points**: External dependencies - **Technical Risks**: Unknowns and mitigation - **Build vs. Buy**: What to develop vs. acquire ## 6. Go-to-Market Strategy - **Pricing Model**: How we capture value - **Distribution Channels**: How users discover us - **Launch Strategy**: Phased rollout plan - **Growth Engine**: How we scale acquisition - **Success Metrics**: Leading and lagging indicators ## 7. Risk Assessment - **Market Risks**: Adoption and competition risks - **Technical Risks**: Feasibility and scalability risks - **Business Risks**: Revenue and operational risks - **Mitigation Strategies**: How to address each risk # Output Format ``` # Product Requirements Document: [Product Name] ## Executive Summary [One-page overview for executives] ## 1. Market Opportunity ### Market Size - TAM: [Total Addressable Market] - SAM: [Serviceable Addressable Market] - SOM: [Serviceable Obtainable Market] ### Competitive Analysis | Competitor | Strengths | Weaknesses | Our Advantage | |------------|-----------|------------|---------------| ### Market Timing [Why now is the right time for this product] ## 2. User Insights ### Primary Persona: [Name] - **Demographics**: [Key attributes] - **Goals**: [What they want to achieve] - **Frustrations**: [Current pain points] - **Success looks like**: [Ideal outcome] ### User Jobs-to-be-Done 1. When [situation], I want to [motivation], so I can [expected outcome] ### User Journey Map [Current experience vs. proposed experience] ## 3. Product Vision ### Elevator Pitch [One compelling sentence] ### Positioning Statement For [target user] who [problem], [Product] is a [category] that [key benefit]. Unlike [alternatives], we [differentiator]. ### Key Value Propositions 1. [Benefit + supporting evidence] 2. [Benefit + supporting evidence] 3. [Benefit + supporting evidence] ## 4. Feature Specification ### Feature 1: [Name] **User Story**: As a [user], I want [capability] so that [benefit] **Acceptance Criteria**: - [ ] Criterion 1 - [ ] Criterion 2 **Priority**: Must-have/Nice-to-have **Effort**: S/M/L **Dependencies**: [Blockers] ### Feature 2: [Name] ... ## 5. Product Roadmap ### Phase 1: MVP (Months 1-3) [Scope and success criteria] ### Phase 2: Scale (Months 4-6) [Scope and success criteria] ### Phase 3: Expand (Months 7-12) [Scope and success criteria] ## 6. Go-to-Market Plan ### Pricing Strategy [Model, tiers, justification] ### Launch Plan [Timeline, channels, tactics] ### Growth Strategy [Acquisition, activation, retention, revenue, referral] ## 7. Success Metrics ### North Star Metric [The one metric that matters most] ### KPI Dashboard | Metric | Target | Measurement | |--------|--------|-------------| ## 8. Risks & Mitigations | Risk | Likelihood | Impact | Mitigation | |------|-----------|--------|------------| ## Appendices ### A. Technical Architecture Overview ### B. Detailed User Research ### C. Competitive Feature Matrix ### D. Financial Projections ``` # Product Strategy Principles - Fall in love with the problem, not the solution - Start narrow, then expand (beachhead strategy) - Build-measure-learn loops - Differentiation matters more than being "better" - Distribution is as important as the product - Validate assumptions before building

Private Notes

Insert Into Your AI

Edit the prompt above then feed it directly to your favorite AI model

Clicking opens the AI in a new tab. Content is also copied to clipboard for backup.