What problem does it solve?
Product strategy often lives in scattered notes or vague tickets, leaving agentic workflows without a durable anchor for what the product is, who it serves, and how success is measured. This Skill interviews the user and writes a short, structured STRATEGY.md at the repository root that downstream planning skills can read as grounding.
Core Features & Use Cases
- Guided strategy interview: Asks sharp questions for five required sections (Target problem, Our approach, Who it's for, Key metrics, Tracks) and pushes back on weak answers like vanity metrics or feature lists.
- Safe update routing: Detects existing files via flowctl status, refuses to overwrite foreign or hand-written STRATEGY.md files without confirmation, and supports section-by-section revision with evidence scans against recent specs.
- Atomic per-section writes: Saves each captured section to disk immediately, so interrupted runs leave a readable partial file that can be resumed later.
- Use Case: A solo founder runs the skill to capture their product's problem, approach, personas, metrics, and tracks in a five-minute doc that later grounds idea generation and planning commands.
Quick Start
Ask the assistant to run the flow-next strategy skill to create or update the repo-root STRATEGY.md for this project.
