# Product Roadmap

> The **product / business plan** — capabilities and milestones, ordered by value.
> The *what* and *why*. Execution (bugs, increments, tasks, SLA) lives in the
> **DevPipeline** (`contextkit/pipeline/`), not here. Built collaboratively via
> `/roadmap`; keep it current as priorities change.
>
> **Convention — P-IDs:** phases are `P1`, `P2`, …; items are `P1.1`, `P1.2`, …
> Each item is a user-facing capability with a one-line acceptance note. Mark
> status with: 📋 planned · ⏳ in progress (a session is on it) · 🟡 partial/blocked ·
> ✅ done — flip an item to ⏳ when a session starts it, to ✅ when it ships.
> Cross-reference DevPipeline tasks by P-ID (a task's `roadmap:` field).

<!-- ROADMAP-NOT-DEFINED -->
_No roadmap defined yet._ Run **`/roadmap`** — in a new project it's built with
you step by step; in an existing project it looks for a roadmap/PRD/spec to
import, or analyzes the code and proposes one for you to refine and extend.

<!--
Example shape once defined:

## P1 — <phase name / theme>
- **P1.1** 📋 <capability> — _accept:_ <one-line done criterion>
- **P1.2** 📋 <capability> — _accept:_ <...>

## P2 — <next phase>
- **P2.1** 📋 <capability> — _accept:_ <...>
-->