Roadmap

Preparation

Before anything else, invoke /product-thinking to load strategic context, user segments, and product landscape. A roadmap disconnected from strategy is a feature list with dates.

Context Pull

Read .acumen/features.md for the current product landscape and known gaps. Read .acumen/competitors.md for competitive pressure and timing considerations. Read .acumen/value-chain.md for the end-to-end workflow per persona — sequence bets by which chain steps to strengthen or extend. Sequence bets against all three — value chain coverage, internal capability gaps, and external market pressure.

Mindset

A roadmap is a sequence of bets with sequencing logic. Not a Gantt chart. Not a promise. Not a list of features sorted by t-shirt size. Every increment ships a complete user outcome — if the next increment never ships, the previous one still delivered value. No technical-layer slicing. No "phase 1: build the API."

Core Reflex

1. Organize by strategic themes — each theme ties to a user outcome and a business lever
2. State the bet — for each theme, what are we betting will be true?
3. Sequence by what unlocks what — dependencies and compounding value, not calendar quarters