# Project Roadmap

> Sequences epics, dependencies, and resources. Use after project-plan for multi-team or multi-quarter Platform delivery.

- Skill: `telum-ai/project-roadmap` (Agent Skill)
- Install (CLI): `npx skillmds@latest add telum-ai/project-roadmap`
- Raw SKILL.md: https://api.skillmd.com/api/skills/telum-ai/project-roadmap/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: telum-ai (https://skillmd.com/u/telum-ai)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/telum-ai/project-roadmap

---



The user input to you can be provided directly by the agent or as a command argument - you **MUST** consider it before proceeding with the prompt (if not empty).

User input:

$ARGUMENTS

## Step 0: Read Template First

**Before any other action** — read this template now using the Read tool:
```
.speck/templates/project/roadmap-template.md
```
The template defines required sections and formatting for `project-roadmap.md`, including timeline tables, dependency notation, and resource allocation format. Generating it from memory produces wrong structure.

**Checkpoint**: After reading, note the top-level sections from the template. Then continue to Step 1.

Create a project-level roadmap that shows epic execution timeline, dependencies, resource allocation, and parallel execution opportunities. This is NOT about development tasks - it's about project management and epic orchestration.

1. Load project planning artifacts:
   - Find active project directory
   - Load PRD.md and epics.md (required)
   - Load any epic-level plans if they exist
   - If missing: ERROR "Run /project-plan first to identify epics"

2. Analyze epic relationships:
   
   **Dependency Types**
   - Hard dependencies (Epic B requires Epic A complete)
   - Soft dependencies (Epic B benefits from Epic A)
   - No dependency (Can run in parallel)
   
   **Risk Assessment**
   - Technical risk (unknowns, complexity)
   - Business risk (user impact, revenue)
   - Integration risk (external dependencies)

3. Determine execution strategy:
   
   **Sequential Strategy** (Level 0-2)
   - One epic at a time
   - Clear handoffs
   - Lower coordination overhead
   
   **Parallel Strategy** (Level 3-4)
   - Multiple epics in flight
   - Requires more coordination
   - Faster overall delivery
   
   **Hybrid Strategy**
   - Critical path sequential
   - Independent work parallel
   - Risk-based approach

4. Generate project roadmap:
   
   **CRITICAL**: Load and follow the template exactly:
   ```
   .speck/templates/project/roadmap-template.md
   ```
   
   Write output to: `[PROJECT_DIR]/project-roadmap.md`

5. Resume the canonical project flow in root `AGENTS.md`; the roadmap owns sequencing, not a second command flow.

Note: This provides project-level orchestration and timeline. Each epic will have its own story breakdown via /epic-breakdown.