
Product Strategist
Turn a fuzzy product direction into a quarterly OKR doc with measurable key results, initiative mapping, and status tables your agent can fill in.
Overview
product-strategist is an agent skill most often used in Validate (also Build, Grow) that produces quarterly OKR planning docs with key results, initiatives, and status tracking tables.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill product-strategistWhat is this skill?
- Structured OKR planning template with quarter, team, owner, and tracking cadence fields
- Per-objective key result tables with baseline, target, current, and On Track / At Risk / Off Track status
- Initiative rows tied to specific KRs with owners, progress, and T-shirt effort sizing
- Company objective linkage so product work rolls up to a single north-star statement
- Repeatable sections for multiple product objectives in one planning doc
- Template supports multiple product objectives each with key result and initiative tables
- Default tracking cadence fields: weekly check-in, monthly review
Adoption & trust: 759 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have product ideas but no shared, measurable quarterly plan tying company goals to initiatives and owners.
Who is it for?
Indie founders and solo PMs drafting quarter plans, KR dashboards, or initiative backlogs before deep build work.
Skip if: Detailed technical implementation plans, market research decks, or pricing experiments without prior outcome framing—pair with research or writing-plans skills instead.
When should I use this skill?
You need quarterly OKR planning, KR baselines and targets, or initiative-to-outcome alignment for a product team doc.
What do I get? / Deliverables
You get a filled OKR planning template with objectives, KR baselines and targets, and initiative mapping ready for weekly or monthly reviews.
- OKR planning markdown with objectives, key results, and initiative tables
- Status-ready doc for weekly check-ins and monthly reviews
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate → scope is the canonical shelf because OKRs force you to define outcomes and boundaries before committing full build capacity. Scope subphase fits objective-setting, KR baselines/targets, and initiative sizing before implementation plans exist.
Where it fits
Draft Q2 objectives and three KRs per bet before committing to a MVP feature list.
Map in-flight features to KR rows with owners and T-shirt effort for sprint planning.
Update Current columns on KRs after pulling activation and retention numbers for a monthly review.
Attach a monetization initiative to a revenue or conversion KR while scoping paid tiers.
How it compares
Strategy template for measurable quarterly outcomes, not a codebase task breakdown or marketing copy generator.
Common Questions / FAQ
Who is product-strategist for?
Solo builders and small teams who own product direction and need OKR-style planning without enterprise tooling.
When should I use product-strategist?
In Validate when scoping a quarter, in Build when aligning features to outcomes, or in Grow when reviewing whether analytics and lifecycle work hit existing KRs.
Is product-strategist safe to install?
It is primarily a document template skill with no implied shell or network access; confirm behavior in your agent and review the Security Audits panel on this page.
SKILL.md
READMESKILL.md - Product Strategist
# OKR Planning Template ## Planning Info | Field | Value | |-------|-------| | **Quarter** | [Q1/Q2/Q3/Q4 YYYY] | | **Team** | [Team Name] | | **Owner** | [Name] | | **Status** | Planning / Active / Complete | | **Tracking Cadence** | Weekly check-in, Monthly review | --- ## Company Objective **[Company-level objective this product work supports]** _Example: "Become the market leader in our category by delivering exceptional customer value"_ --- ## Product Objective 1: [Objective Title] _[Qualitative, inspirational statement. What does success look like?]_ ### Key Results | # | Key Result | Baseline | Target | Current | Status | |---|-----------|----------|--------|---------|--------| | 1.1 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | | 1.2 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | | 1.3 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | ### Initiatives | Initiative | Key Result | Owner | Status | Effort | |-----------|-----------|-------|--------|--------| | [Feature/project name] | KR 1.1 | [Name] | Not Started / In Progress / Complete | [T-shirt size] | | [Feature/project name] | KR 1.2 | [Name] | Not Started / In Progress / Complete | [T-shirt size] | --- ## Product Objective 2: [Objective Title] _[Qualitative, inspirational statement]_ ### Key Results | # | Key Result | Baseline | Target | Current | Status | |---|-----------|----------|--------|---------|--------| | 2.1 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | | 2.2 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | | 2.3 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | | 2.4 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | ### Initiatives | Initiative | Key Result | Owner | Status | Effort | |-----------|-----------|-------|--------|--------| | [Feature/project name] | KR 2.1 | [Name] | Not Started / In Progress / Complete | [T-shirt size] | | [Feature/project name] | KR 2.2 | [Name] | Not Started / In Progress / Complete | [T-shirt size] | --- ## Product Objective 3: [Objective Title] _[Qualitative, inspirational statement]_ ### Key Results | # | Key Result | Baseline | Target | Current | Status | |---|-----------|----------|--------|---------|--------| | 3.1 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | | 3.2 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | | 3.3 | [Measurable outcome] | [Current value] | [Target value] | [Progress] | On Track / At Risk / Off Track | ### Initiatives | Initiative | Key Result | Owner | Status | Effort | |-----------|-----------|-------|--------|--------| | [Feature/project name] | KR 3.1 | [Name] | Not Started / In Progress / Complete | [T-shirt size] | --- ## Tracking ### Weekly Check-In Format - **Confidence level** (1-10) for each key result - **Blockers** identified and escalated - **Adjustments** to initiatives if needed ### Monthly Review Format - **Progress update** on all key results with data - **Initiative status** review - **Risk assessment** and mitigation updates - **Stakeholder communication** summary ### End-of-Quarter Scoring Score each key result 0.0 - 1.0: - **1.0:** Fully achieved - **0.7:** Strong progress, nearly there (ideal target) - **0.4:** Meaningful progress but missed target - **0.0:** No progress _Note: Consistently scoring 1.0 means OKRs are not ambitious enough. Target 0.6-0.7 average._ { "metadata": { "strategy": "growth", "quarter": "Q1 2025", "generated_at": "2025-01-15T10:30:00Z", "teams": ["Growth", "Platform", "Mobile", "Data"]