Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling. Use for strategic planning, goal alignment, competitive analysis, and organizational design.
Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling. Use for strategic planning, goal alignment, competitive analysis, and organizational design.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Strategic toolkit for Head of Product to drive vision, alignment, and organizational excellence.
CapabilityDescriptionToolOKR CascadeGenerate aligned OKRs from company to team levelokr_cascade_generator.pyAlignment ScoringMeasure vertical and horizontal alignmentBuilt into generatorStrategy Templates5 pre-built strategy typesGrowth, Retention, Revenue, Innovation, OperationalTeam ConfigurationCustomize for your org structure--teams flag
# Growth strategy with default teams python scripts/okr_cascade_generator.py growth # Retention strategy with custom teams python scripts/okr_cascade_generator.py retention --teams "Engineering,Design,Data" # Revenue strategy with 40% product contribution python scripts/okr_cascade_generator.py revenue --contribution 0.4 # Export as JSON for integration python scripts/okr_cascade_generator.py growth --json > okrs.json
StrategyWhen to UseGrowthScaling user base, market expansionRetentionReducing churn, improving LTVRevenueIncreasing ARPU, new monetizationInnovationMarket differentiation, new capabilitiesOperationalImproving efficiency, scaling operations See references/strategy_types.md for detailed guidance.
{ "current": 100000, // Current MAU "target": 150000, // Target MAU "current_nps": 40, // Current NPS "target_nps": 60 // Target NPS }
# Default teams python scripts/okr_cascade_generator.py growth # Custom org structure with contribution percentage python scripts/okr_cascade_generator.py growth \ --teams "Core,Platform,Mobile,AI" \ --contribution 0.3
ScoreTargetAction if BelowVertical Alignment>90%Ensure all objectives link to parentHorizontal Alignment>75%Check for team coordination gapsCoverage>80%Validate all company OKRs are addressedBalance>80%Redistribute if one team is overloadedOverall>80%<60% needs restructuring
Before finalizing: Review generated objectives with stakeholders Adjust team assignments based on capacity Validate contribution percentages are realistic Ensure no conflicting objectives across teams Set up tracking cadence (bi-weekly check-ins) # Export JSON for tools like Lattice, Ally, Workboard python scripts/okr_cascade_generator.py growth --json > q1_okrs.json
python scripts/okr_cascade_generator.py [strategy] [options] Strategies: growth | retention | revenue | innovation | operational
OptionDescriptionDefault--teams, -tComma-separated team namesGrowth,Platform,Mobile,Data--contribution, -cProduct contribution to company OKRs (0-1)0.3 (30%)--json, -jOutput as JSON instead of dashboardFalse--metrics, -mMetrics as JSON stringSample metrics
Dashboard Output (growth strategy) ============================================================ OKR CASCADE DASHBOARD Quarter: Q1 2025 | Strategy: GROWTH Teams: Growth, Platform, Mobile, Data | Product Contribution: 30% ============================================================ ๐ข COMPANY OKRS ๐ CO-1: Accelerate user acquisition and market expansion โโ CO-1-KR1: Increase MAU from 100,000 to 150,000 โโ CO-1-KR2: Achieve 50% MoM growth rate โโ CO-1-KR3: Expand to 3 new markets ๐ CO-2: Achieve product-market fit in new segments ๐ CO-3: Build sustainable growth engine ๐ PRODUCT OKRS ๐ PO-1: Build viral product features and market expansion โณ Supports: CO-1 โโ PO-1-KR1: Increase product MAU to 45,000 โโ PO-1-KR2: Achieve 45% feature adoption rate ๐ฅ TEAM OKRS Growth Team: ๐ GRO-1: Build viral product features through acquisition and activation โโ GRO-1-KR1: Increase product MAU to 11,250 โโ GRO-1-KR2: Achieve 11.25% feature adoption rate ๐ฏ ALIGNMENT SCORES โ Vertical Alignment: 100.0% ! Horizontal Alignment: 75.0% โ Coverage: 100.0% | โ Balance: 97.5% | โ Overall: 94.0% โ Overall alignment is GOOD (โฅ80%) JSON Output (retention --json, truncated) { "quarter": "Q1 2025", "strategy": "retention", "company": { "objectives": [ { "id": "CO-1", "title": "Create lasting customer value and loyalty", "key_results": [ { "id": "CO-1-KR1", "title": "Improve retention from 70% to 85%", "current": 70, "target": 85 } ] } ] }, "product": { "contribution": 0.3, "objectives": ["..."] }, "teams": ["..."], "alignment_scores": { "vertical_alignment": 100.0, "horizontal_alignment": 75.0, "coverage": 100.0, "balance": 97.5, "overall": 94.0 } } See references/examples/sample_growth_okrs.json for a complete example.
DocumentDescriptionreferences/okr_framework.mdOKR methodology, writing guidelines, alignment scoringreferences/strategy_types.mdDetailed breakdown of all 5 strategy types with examplesreferences/examples/sample_growth_okrs.jsonComplete sample output for growth strategy
Limit to 3-5 objectives per level, each with 3-5 key results Key results must be measurable with current and target values Validate parent-child relationships before finalizing
Target >80% overall alignment; investigate any score below 60% Balance scores ensure no team is overloaded Horizontal alignment prevents conflicting goals across teams
Configure teams to match your actual org structure Adjust contribution percentages based on team size Platform/Infrastructure teams often support all objectives Specialized teams (ML, Data) may only support relevant objectives
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Largest current source with strong distribution and engagement signals.