ce-strategy

Run the skill and answer its interview questions covering target problem, approach, primary user, key metrics, and tracks. It pushes back on weak answers, drafts the document from a fixed template, and writes it to STRATEGY.md at your repo root.

The template includes target problem, our approach, who it's for, key metrics (3-5), and tracks (2-4), plus optional milestones, not-working-on, and marketing sections. Section order is locked and optional sections are deleted if unused.

Yes. Pass a section name like metrics or approach as an argument, and the skill re-interviews only that section while preserving everything else. It also refreshes the last_updated date in the frontmatter.

The skill follows Richard Rumelt's kernel of diagnosis, guiding policy, and coherent action. It rejects fluff, goals stated as strategy, vanity metrics, and feature lists in place of a guiding choice, pushing for falsifiable problems and clear commitments.

No. It only produces the strategy anchor document. Backlog prioritization, product requirements, and implementation plans are handled by separate workflows such as ce-brainstorm and ce-plan.