This creates and maintains STRATEGY.md at your repo root, a structured document that captures what your product is, who it's for, and where you're investing. It works through an interview that asks sharp questions about target problem, approach, persona, metrics, and tracks, then pushes back on weak answers instead of transcribing whatever you say. The structure comes from Rumelt's strategy kernel, so it enforces actual strategic choices rather than feature lists or goals dressed up as direction. Rerunnable: second time through it updates specific sections and preserves what's working. Downstream skills like ce-ideate and ce-brainstorm read it as grounding when they run.
npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-strategy