ce-strategy
Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.
Install
With your agent
Install OMGSkills skill "everyinc/compound-engineering-plugin:ce-strategy" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/EveryInc/compound-engineering-plugin /tmp/compound-engineering-plugin && ln -s /tmp/compound-engineering-plugin/skills/ce-strategy ~/.claude/skills/ce-strategyFrom README
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.
More from this repo
ce-brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only unified plan.
ce-babysit-pr
Babysits an open GitHub PR until merge-ready, first judging whether an old PR still belongs.
ce-commit
Used to create a git commit with a clear, value-communicating message.