ce-strategy

To create a durable product strategy document, this Skill generates a STRATEGY.md file at your repo root. It captures the target problem, approach, user focus, metrics, and tracks through an interview-driven workflow to ground your product direction.

A strategy file should include sections for the target problem, your approach, who it's for, key metrics, and tracks. This Skill produces a STRATEGY.md document matching this exact structure to serve as a canonical anchor for stakeholders.

To update an existing strategy document, this Skill reconciles new inputs over multiple runs. It preserves strong content from previous sessions while updating stale sections and refreshing the last_updated field in STRATEGY.md.

The best way to gather strategy inputs is through a structured interview process. This Skill guides Phase 1 and Phase 2 interviews with grounded prompts and pushback rules to extract problem, approach, user, metrics, and tracks data effectively.

Yes, you can use this strategy documentation Skill for a new product. It is explicitly applied when starting a new product to set up the initial STRATEGY.md, ensuring direction is grounded from day one.

No dependencies are required to set up a strategy doc with this approach. The Skill operates independently to generate and maintain the STRATEGY.md file, requiring only your repository workspace to anchor the document.