10x-roadmap

Generates a dependency-ordered roadmap of vertical slices from a PRD.

Updated May 20, 2026
One-click install
npx skills add https://github.com/ZawilecxD/trAInR --skill 10x-roadmap-zawilecxd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 10x-roadmap
Source: https://github.com/ZawilecxD/trAInR/tree/main/.cursor/skills/10x-roadmap
Command: npx skills add https://github.com/ZawilecxD/trAInR --skill 10x-roadmap-zawilecxd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a finished PRD into an actionable build order is hard: teams either plan horizontally (database first, then API, then UI) or guess at sequencing. This Skill reads a PRD, probes the existing codebase, and produces a roadmap of vertical, user-visible slices ordered by dependency. ## Core Features & Use Cases - PRD readiness scoring: Applies a 4-signal heuristic (vision, user stories, must-have FRs, business logic) before generating, warning when the PRD is too thin to roadmap. - Automated codebase baseline: Probes frontend, backend, data, auth, deploy, and observability layers via parallel subagents, reporting present/absent/partial with file evidence. - Lean framing interview: Asks at most three anchor questions (main goal, north-star slice, top blocker), each with a grounded recommendation and reasoned alternatives, then derives investment areas. - Use Case: After finishing a PRD for a fitness coaching app, run the Skill to get a roadmap.md listing foundation items (auth scaffold, deploy skeleton) and vertical slices (workout logging, progress dashboard) in dependency order, ready to hand each slice to a per-change planner. ## Quick Start Ask the AI to generate the roadmap from context/foundation/prd.md after your PRD is complete.

Frequently Asked Questions about 10x-roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a PRD into a development roadmap?▼

Run the Skill after your PRD exists at context/foundation/prd.md. It reads the PRD fully, probes the codebase baseline, asks 2-3 framing questions with recommendations, and writes a roadmap.md of vertical slices in dependency order.

What is a vertical slice in product roadmapping?▼

A vertical slice is one user-visible capability delivered end-to-end across data, logic, and interface layers, such as "user can log a workout". The Skill explicitly rejects horizontal slicing like building the whole database layer first.

When should I not generate a roadmap from a PRD?▼

Skip it when the PRD is hollow, meaning large open-question sections or TODO placeholders, since the roadmap inherits that hollowness. Also skip it for planning a single change in detail, which belongs to a per-change planning skill.

Does the roadmap include time estimates or deadlines?▼

No. The Skill never assigns time estimates, t-shirt sizes, points, or calendar dates. It expresses ordering purely as a dependency graph and marks slices that can run in parallel.

How does the Skill assess what is already built in the codebase?▼

It fans out parallel subagent 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, which you confirm before it shapes the roadmap.