ce-strategy

Create and maintain a STRATEGY.md product strategy document through structured interviews.

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill ce-strategy-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-strategy
Source: https://github.com/mmnavarr/harness/tree/main/skills/ce-strategy
Command: npx skills add https://github.com/mmnavarr/harness --skill ce-strategy-mmnavarr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams often lack a clear, durable strategy document, leading to unfocused roadmaps and feature lists masquerading as strategy. This Skill interviews you with sharp questions and pushback to produce a concise STRATEGY.md covering the target problem, approach, users, metrics, and tracks of work. ## Core Features & Use Cases - Guided Strategy Interview: Asks one question at a time across eight sections, pushing back on weak answers like vanity metrics, vague personas, and feature lists disguised as strategy. - Rerunnable Updates: Detects an existing STRATEGY.md and updates only the sections you target, preserving what still works and refreshing the last_updated date. - Downstream Grounding: Produces a canonical repo-root document that ce-ideate, ce-brainstorm, and ce-plan read as context on their next run. - Use Case: When starting a new product, run the skill to answer questions about the core problem and guiding approach, then receive a complete STRATEGY.md draft for review before it is written to the repo root. ## Quick Start Ask the AI to write our product strategy doc using the ce-strategy skill.

Frequently Asked Questions about ce-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product strategy document with AI?▼

Run the ce-strategy skill, which interviews you section by section on the target problem, approach, users, metrics, and tracks. It pushes back on vague answers, drafts the full document for review, then writes STRATEGY.md to your repository root.

What sections should a product strategy document include?▼

The template covers target problem, our approach, who it's for, key metrics, and tracks as required sections. Milestones, not-working-on items, and marketing positioning are optional and deleted if unused.

Can I update only one section of an existing strategy doc?▼

Yes. Pass a section name like metrics or approach as an argument, and the skill re-interviews only that section with full pushback while preserving everything else and refreshing the last_updated date.

What makes a good product strategy versus a bad one?▼

The skill applies Rumelt's strategy kernel: a diagnosis of the problem, a guiding policy, and coherent actions. It rejects fluff, goals stated as strategy, vanity metrics, and feature lists in place of a guiding choice.

Does the strategy skill prioritize my backlog or write requirements?▼

No. It only produces the strategy anchor document. Backlog prioritization, product requirements, and implementation plans belong to separate workflows like ce-brainstorm and ce-plan.