10x-roadmap

Invoke the skill after your PRD exists at context/foundation/prd.md, optionally passing a custom path. It reads the PRD, probes the codebase baseline, asks up to three framing questions, then writes context/foundation/roadmap.md with ordered vertical slices.

A vertical slice is a single user-visible capability that touches every layer needed to make it real: data, logic, and interface. The skill explicitly avoids horizontal slicing like a separate database slice or API slice, which delays user-visible value.

Skip it when the PRD scores below 3 on the readiness heuristic, meaning it lacks a vision, populated user stories, must-have requirements, or business logic. Also skip it when you want to plan a single change in detail, which is the job of the per-change planning skill.

No. The skill never assigns time estimates, t-shirt sizes, story points, or calendar dates. It expresses ordering purely as a dependency graph and marks slices that can be executed in parallel by separate agent runs.

It runs parallel probes across six layers: frontend, backend/API, data, auth, deploy/infra, and observability. Each probe returns a present, absent, or partial verdict with file evidence, and layers already declared in tech-stack.md are reported without re-probing.

When a change whose ID matches a roadmap item is archived, the archive skill flips that item's status to done and appends an entry to the roadmap's Done section. The roadmap skill itself never pre-populates completed items.