Roadmap

The roadmap is where every feature starts. It holds what you are building, why and in what order, and it is the only place to start a cycle.

Purpose

The roadmap is a permanent, project-level board that exists outside any single cycle. Features are created here and move through a lifecycle as they become better defined. It answers three questions: what are we building, why, and in what order?

The roadmap chat acts as a product manager. It helps with personas, user value, done whens, scope and visual direction, but it deliberately leaves technology choices to the engineering lead AI in cycle planning.

Why We Built This

AI can build the wrong thing quickly. The roadmap makes sure a feature has a clear audience and purpose before any code is written.

•Product discipline — A feature can't reach Ready without a persona and a user value statement, and the AI can't bypass that
•One source of truth — There is no separate backlog: anything deferred becomes a feature in the Later lane
•Safe ordering — Dependency checks stop a feature being promoted ahead of something it relies on

Working with the Roadmap

Add Features

Create features directly or through the roadmap chat. Each one starts as an Idea in the Now, Next or Later lane.

Define Them

Add done whens, a technical approach and at least one task to reach Defined. Assign a persona and write a user value statement to reach Ready.

Prioritise

Drag features between lanes, or use the sortable list view. Priority (Now, Next, Later) and status (how ready a feature is) are independent.

Start a Cycle

Click Start Cycle. The AI recommends up to 3 Ready features from the Now lane that make sense together, and shows a cost and duration estimate before you confirm.

Key Features

Board and List Views

A Now, Next and Later board with an In Cycle strip and a collapsible Shipped section, or a sortable, filterable list.

Personas

Named user personas per project, seeded with End User, Admin and Developer. The AI can draft descriptions and suggest personas for a feature.

Dependencies

Explicit feature-to-feature dependencies with circular-dependency detection.

Visual Direction

The product manager AI offers colour theme, font and design direction pickers. These choices always come from you, never silently from the AI.

Designs

A project-wide gallery of generated wireframes and the shared component library.

Feature Lifecycle

A feature's status shows how far along it is:

Idea

Captured, but not yet defined.

Defined

Has done whens, a technical approach and at least one task.

Ready

Also has a persona and a user value statement, so it can go into a cycle.

In Cycle

Being planned or built. It is locked on the roadmap and edited from the cycle.

In Review

Built and waiting for human review.

Shipped

Delivered, and grouped by the cycle that shipped it.

PM Mode

Each project has a dial that controls how much the AI challenges weak scope and vague criteria:

Off

A neutral executor with no product pushback.

BalancedDefault

A product peer that challenges with reasoning, then defers to you.

Sharp

A demanding peer with a lower threshold for pushback.

Frequently Asked Questions

Where is the backlog?

The Later lane is the backlog. Defects and missed items deferred from review become features in that lane.

Can I create features inside a cycle?

New features are created on the roadmap. During a cycle, the planning AI can only add cycle-local defects or queue a feature for the next cycle.

How many features can a cycle hold?

Up to 3. The cap keeps cycles focused and reviewable.