ce-strategy
Create or update STRATEGY.md. Use when starting a product, adding a strategy doc to an existing repo, changing direction or roadmap, or when ce-ideate, ce-brainstorm, or ce-plan need upstream product grounding.
Install
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 owns 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.