Context Slice Strategy Type Recognition
Match user intent to the appropriate guide:
| User says | Strategy Type | Guide |
|---|---|---|
| "prioritize", "rank features", "roadmap", "what to build first" | Prioritization | Prioritization Guide |
| "pricing", "monetization", "revenue model", "freemium", "upsell" | Monetization | Monetization Guide |
| "vision statement", "product vision", "north star", "mission" | Vision | Vision Statement Guide |
| "brainstorm", "feature ideas", "from feedback", "what to build" | Ideation | Feature Ideation Guide |
| "A/B test", "experiment", "hypothesis", "test design" | Experimentation | Experimentation Guide |
Task Routing
For complex strategic work with structured inputs, use the dedicated task:
| Strategy Type | Route To |
|---|---|
| Roadmap Prioritization |  Prioritize Roadmap |
All other strategy types use slice guidance directly.
Product Context Profile
Check 
Product Context Profile before any strategic work. Context matters for:
- Company stage → Affects prioritization criteria (growth vs retention)
- User personas → Shapes feature ideation and experiment targeting
- Competitive landscape → Informs differentiation in monetization
- Strategic goals → Alignment check for all recommendations
If the user shares strategic context not already in the profile, offer to save it:
"Want me to save this strategic context to your product profile?"
Gathering Context
Each strategy type needs specific context. If missing, check Product Context Profile first, then ask the user.
For Prioritization:
- List of initiatives with any existing scores
- Criteria that matter (impact, effort, strategic fit)
- Constraints (resources, timeline, dependencies)
For Monetization:
- Current pricing model
- Target customer segments
- Competitive pricing landscape
- Business goals (growth vs profitability)
For Vision:
- Long-term product goals
- User needs being served
- Company mission/values
For Ideation:
- Customer feedback source (surveys, tickets, interviews)
- Strategic priorities to guide brainstorming
- Constraints on solution space
For Experimentation:
- Changes being considered
- Current metrics and baselines
- User segments available for testing
Output Behavior
- Identify strategy type from user request
- Load the relevant guide slice
- Gather any missing required context
- Apply frameworks and provide structured analysis
- End with clear recommendations and next steps
For prioritization, output structured tables with scoring.
For monetization, output comparisons with pros/cons.
For ideation, output ranked feature ideas with rationale.
For experiments, output complete test specifications.
When Ambiguous
Strategic questions often overlap. Ask:
"Are you looking for [interpretation A] or [interpretation B]?"