Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
Creates or updates a repo-root STRATEGY.md through an interview, capturing what the product is, who it serves, and where the team invests.
Install Product Strategy Document
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ce-strategy .claude/skills/ce-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ce-strategy" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-strategy into .claude/skills/ce-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/ce-strategy .agents/skills/ce-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ce-strategy" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-strategy into .agents/skills/ce-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/ce-strategy .cursor/skills/ce-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ce-strategy" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-strategy into .cursor/skills/ce-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/EveryInc/compound-engineering-plugin.git --path skills/ce-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/ce-strategy .gemini/skills/ce-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ce-strategy" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-strategy into .gemini/skills/ce-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install EveryInc/compound-engineering-plugin ce-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/ce-strategy .github/skills/ce-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ce-strategy" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-strategy into .github/skills/ce-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EveryInc/compound-engineering-plugin ce-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/ce-strategy .opencode/skills/ce-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ce-strategy" agent skill from https://github.com/EveryInc/compound-engineering-plugin/tree/main/skills/ce-strategy into .opencode/skills/ce-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ce-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ce-strategy- GitHub stars
- 25k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 1,172 words
- Files
- 5 (incl. references)
- Skills in repo
- 37
- Repo updated
- First seen
- Licence
- MIT
At a glance
Creates or updates a repo-root STRATEGY.md through an interview, capturing what the product is, who it serves, and where the team invests.
- Works in 4 steps: Ground and route → First-run interview → Update run → …
- Starting a new product and needing a first strategy document
- SKILL.md covers Boundaries, Asking and routing, Phase 0: Ground and route and Phase 1: First-run interview, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
A defined set of sections in a shared STRATEGY.md file is this skill's own territory, in a file that other skills also read: an ideation skill checks whether proposed work is on-strategy, a planning skill does the same, and others pull the product name, key metrics, or primary persona from it. Only the sections its template names get written, with new meaning merged into an existing section rather than duplicated when another skill already owns that heading.
You answer the substantive questions; the repository only grounds a sharper question, never fills in an answer for you. The document anchors what the product is and why, explicitly pushing features, schedules, and implementation plans out to other tools rather than letting the strategy document absorb them.
When your agent uses it
- Starting a new product and needing a first strategy document
- Refreshing an existing STRATEGY.md after a change in direction
- Checking whether proposed work is still on-strategy
Example prompts
- “Start a STRATEGY.md for our new billing product.”
- “Update STRATEGY.md now that we're pivoting to a usage-based model.”
- “Is the proposed SSO feature on-strategy per our current STRATEGY.md?”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 67035e9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Product Strategy Document loads about 1.9k tokens when it runs, and up to ~9.3k if it reads all its reference files. Until then it costs about 32 tokens; SKILL.md has 1,172 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from EveryInc/compound-engineering-plugin at commit 67035e9, republished under its MIT licence (© EveryInc). 1,172 words, ~1,914 tokens.
Download SKILL.mdSave it as
.claude/skills/ce-strategy/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- ce-strategy
- description
- Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.
- argument-hint
- [optional: section to revisit, e.g. 'metrics' or 'approach']
Product Strategy
The current year is 2026 - use it when dating the document.
ce-strategy writes and maintains its part of STRATEGY.md - the repo-root project document that captures what the project is, who it serves, how it succeeds, and where the team is investing. The file is shared with other tools and people; this skill writes only the sections references/strategy-template.md names. Downstream skills read it when it exists: ce-ideate, ce-brainstorm, and ce-plan for what work is on-strategy; ce-product-pulse for the product name and key metrics; ce-dogfood for the primary persona. Its frontmatter keys and this skill's section headings are the contract those skills parse - keep them for every section this skill authors; a meaning an existing section already carries is merged into it (references/update-run.md).
Done: STRATEGY.md exists at the repo root and the user has seen what will be written and had an edit pass. For a file in this skill's house format, every required section is filled from answers that survived pushback (or explicitly deferred to a linked legacy doc) and the file matches references/strategy-template.md. For a file in any other shape, done is the user-approved minimal edits applied, with the document's shape unchanged. A section the user could not sharpen in two rounds is written as given and named in chat as worth revisiting - a completed run, not a blocked one.
Boundaries
- Anchor, not plan. Strategy is what the product is and why. Features belong in
ce-brainstorm, schedules and prioritization in the issue tracker, implementation plans ince-plan; do not let them creep into the doc, and do not update the tracker or reconcile in-flight work. - The user answers; the repo only grounds the question. Use evidence to ask a sharper question, never to fill in a section. Do not derive the strategy from the repo.
- Short is a feature. Push back on expansion rather than adding sections.
- Record which metrics matter and where they live, not what they read today.
- Meaning is the contract; the shape belongs to whoever created the doc. A file that is solely this skill's (
references/update-run.mdstates the test) is maintained in house format on every write: headings renamed, sections in the template's current order, missing required sections offered. Do not treat it as multi-writer merely because the file is shared in principle. A file in any other shape, hand-written or from another tool, is read by meaning and edited in its own shape and idiom: no restructuring into the template, no uninvited frontmatter or headings. Either way, two things are never edited: a section carrying an author-approved marker (e.g.<!-- <tool>: author-approved 2026-07-10 -->), and a doc the user does not own. For those, report the conflict, or write a separate file that links to it. A targeted update preserves every other section's content exactly. Where that section sits follows the same ownership test: a solely-owned file takes the template's order; a multi-writer file is never reordered.references/update-run.mddefines the rest and is a required read before you edit an existing file.
Asking and routing
Ask one question at a time through the host's blocking question tool already in the current tool list. Match by capability; never probe a user-facing tool to discover it. Fall back to numbered options on the visible chat surface only when no such tool is listed or a real question call errors. Never silently skip the question.
Any argument this skill was invoked with — present in the current prompt or conversation, from the user or a calling skill — is a focus hint: a section to revisit (metrics, positioning, tracks; older names such as approach or who it's for map to the current section) or a scope hint. With none, proceed open-ended and let the file state decide the path.
Show full SKILL.md (556 more words)Show less
Phase 0: Ground and route
Phase 0 produces a repo model and a decision about which phase runs next, whatever the harness reads. references/grounding.md is a non-optional load: it carries the full source list and the wording of the disagreement question and the focus hint.
The repo model is your working understanding of what this product is. Read STRATEGY.md if it exists. Take what the product is from its stated intent and structure - README, CONCEPTS.md, docs/, sibling docs such as PRODUCT.md, what the code is organized around - and bound that read to "what is this and who is it for" rather than profiling the whole repo. Take what is getting attention now from recent commits or PRs. Attention informs only the Tracks question and staleness in an update run; where it disagrees with stated intent, that is a question for the user, never a conclusion. Show the model in chat before the first question: three to five lines on what you take the product to be, who it seems to serve, and where attention has gone, each with its source named, and invite correction. If the model did not supply the product's name, ask for it here - the template's frontmatter and title need it. A repo with no substantive content is a normal path: say so in one line and run the interview ungrounded.
The next phase is announced in one line by file state: no file -> Phase 1 ("Strategy doc not found - let's write it."), after the legacy-sibling offer in references/grounding.md when one applies; file exists -> Phase 2 ("Found existing strategy - let's review and update.").
Phase 1: First-run interview
Read references/interview.md before the first question - a non-optional load. The opening questions, pushback rules, anti-pattern examples, quality bar, blocking-question tool per host, and the two-round cap live there; improvising from memory produces a passive transcription instead of a strategy doc.
Run the interview in this order (the document itself follows the template's order; Boundaries is asked after the stress test, where its content comes from):
- Purpose
- Positioning
- Users
- Key metrics
- Tracks
- Stress test
- Boundaries (always written)
- Milestones (optional)
- Brand (optional)
When every section is captured, read references/strategy-template.md, fill it in, present the full draft in chat, offer one round of edits, then write STRATEGY.md.
Phase 2: Update run
Read references/update-run.md first - a non-optional load, before the summary, the drift check, or any question. It decides how drift candidates are raised, which section is revisited, and what is preserved untouched. An update run summarizes the file's current state in 3-5 lines, and names any section the repo model suggests is stale as a candidate rather than a verdict. It then revisits the section the focus hint named, or the one the user picks when asked. The user may pick any section; list the drift candidates first, as suggestions rather than as the only choices. Every other section's content is left untouched, and its place follows the ownership test in references/update-run.md. Questions and pushback still come from references/interview.md, applied as if this were a first run.
Phase 3: Downstream handoff
Note in one line where the file lives and that ce-ideate, ce-brainstorm, and ce-plan pick it up as grounding on their next run. If no downstream skill has run here yet, suggest ce-ideate or ce-brainstorm as a next step.
© EveryInc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/ce-strategy of EveryInc/compound-engineering-plugin.
- SKILL.md
- references/grounding.md
- references/interview.md
- references/strategy-template.md
- references/update-run.md
Open the folder on GitHubat commit 67035e9
Compare with similar skills
Product Strategy Document next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Product Strategy Document this skillEveryInc/compound-engineering-plugin | 25k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Company Research Briefdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~3.8k | Automated safety check: Pass | Custom licence | |
| Organic Growth Path Advisordeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~5.2k | Automated safety check: Pass | Custom licence | |
| Product Strategistalirezarezvani/claude-skills | 28k | 2 repos | ~1.8k | Automated safety check: Pass | MIT | |
| PlaidBuildGreatProducts/plaid | 217 | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Company Research Brief
deanpeters/Product-Manager-Skills
Builds a company research brief covering executive quotes, product strategy, transformation efforts and org context, tailored to interview prep, competitor or partnership work.
Organic Growth Path Advisor
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
Plaid
BuildGreatProducts/plaid
Product Led AI Development — guides founders from idea to launched product.
Product Competitive Analysis
Fokkyp/claude-skills
Produces product-manager competitive analysis reports in Chinese, with a confirm-first scoping gate, three-phase evidence collection and single or multi-product modes.
More from EveryInc/compound-engineering-plugin
All 37 skills in this repoCompound Learning Writer
EveryInc/compound-engineering-plugin
Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.
Compound Learnings Refresh
EveryInc/compound-engineering-plugin
Audits a repo's stored learnings against the current codebase, fixes stale, overlapping or superseded docs and reports on every document.
Compound Engineering Prototype
EveryInc/compound-engineering-plugin
Builds a throwaway prototype at just the fidelity needed to settle a specific how-it-should-work-or-feel question, before committing to an approach other work will treat as fixed.
Compound Engineering Setup
EveryInc/compound-engineering-plugin
Checks Compound Engineering plugin health and repo-local config, or scaffolds a Compound Pack when you ask for one by id.
PR Babysitter
EveryInc/compound-engineering-plugin
Watches an open GitHub pull request over time, routing review comments and CI failures to other skills until the PR is ready to merge.
CE Brainstorm
EveryInc/compound-engineering-plugin
Turns a vague or ambitious feature idea into a requirements-only plan through dialogue with you, sized to the work, before any code is written.
Related
Categories
Questions about Product Strategy Document
What does Product Strategy Document do?
Creates or updates a repo-root STRATEGY.md through an interview, capturing what the product is, who it serves, and where the team invests. md file is this skill's own territory, in a file that other skills also read: an ideation skill checks whether proposed work is on-strategy, a planning skill does the same, and others pull the product name, key metrics, or primary persona from it. Only the sections its template names get written, with new meaning merged into an existing section rather than duplicated when another skill already owns that heading.
When should I use Product Strategy Document?
Product Strategy Document fits situations like: starting a new product and needing a first strategy document; refreshing an existing STRATEGY.md after a change in direction; checking whether proposed work is still on-strategy.
How do I install Product Strategy Document in Claude Code?
Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-strategy -a claude-code`. Or copy the skill folder (skills/ce-strategy in EveryInc/compound-engineering-plugin) into .claude/skills/ce-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Product Strategy Document in Codex?
Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-strategy -a codex`. Or copy the skill folder (skills/ce-strategy in EveryInc/compound-engineering-plugin) into .agents/skills/ce-strategy in your project. Codex loads it when a task matches its description.
Can I use Product Strategy Document in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EveryInc/compound-engineering-plugin --skill ce-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ce-strategy, .gemini/skills/ce-strategy, .github/skills/ce-strategy and .opencode/skills/ce-strategy in your project.
What does Product Strategy Document need to run?
SKILL.md names no scripts, command-line tools or credentials: Product Strategy Document is instructions for the agent only.
Does Product Strategy Document access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Product Strategy Document safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Product Strategy Document use?
Product Strategy Document is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Product Strategy Document use?
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.4k tokens, read only when the agent opens those files.
What are the alternatives to Product Strategy Document?
Skills that share tags, products or a category with Product Strategy Document: Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), Company Research Brief (deanpeters/Product-Manager-Skills, 7.2k stars), Organic Growth Path Advisor (deanpeters/Product-Manager-Skills, 7.2k stars) and Product Strategist (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Product Strategy Document?
EveryInc (a GitHub organization) maintains it in EveryInc/compound-engineering-plugin, which has 25,424 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 8, 2026.
Source: EveryInc/compound-engineering-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.