roadmap-orchestrator

roadmap-orchestrator is an agent for Claude Code from evan043/claude-cli-advanced-starter-pack. It costs 37 tokens per session (4,071 once invoked), scanned A, original, MIT.

A coordinator for several phase plans within one roadmap. It divides a roadmap into manageable development plans and tracks dependencies between them.

In plain words
What is it for?
It helps analyze roadmap scope, create phase plans for areas such as authentication or testing, coordinate those plans, manage dependencies, and report when the roadmap is complete.
Why use it?
It helps teams organize related work when different parts must be completed in a particular order or by different specialists.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: names the TodoWrite tool.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/evan043/claude-cli-advanced-starter-pack/roadmap-orchestrator.template
Clone the repo
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-pack

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for roadmap-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/evan043/claude-cli-advanced-starter-pack/roadmap-orchestrator.template.svg)](https://agentmods.dev/agents/evan043/claude-cli-advanced-starter-pack/roadmap-orchestrator.template)
Your own site
<a href="https://agentmods.dev/agents/evan043/claude-cli-advanced-starter-pack/roadmap-orchestrator.template"><img src="https://agentmods.dev/badge/agents/evan043/claude-cli-advanced-starter-pack/roadmap-orchestrator.template.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,071 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.04071
Opus 5 $0.00018 $0.02035
Sonnet 5 $0.00007 $0.00814
Haiku 4.5 $0.00004 $0.00407

Measured 6d ago against content hash c9afca732ff5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

roadmap-orchestrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/agents/roadmap-orchestrator.template.md · 523 lines

How it starts

The opening of the file, as written. The whole thing — 523 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Roadmap Orchestrator

You are the Roadmap Orchestrator (L1) responsible for coordinating MULTIPLE phase-dev-plans within a single roadmap. Your job is to analyze roadmap scope, determine the right phase-dev-plans, spawn /phase-dev-plan for each, and track completion across all plans.

Core Responsibilities

  1. Analyze roadmap scope and determine how many phase-dev-plans are needed
  2. Determine plan slugs (e.g., /auth-backend, /auth-frontend, /auth-testing)
  3. Spawn /phase-dev-plan for each slug with parent roadmap context
  4. Track plan completion via child PROGRESS.json references
  5. Manage cross-plan dependencies (e.g., auth-frontend waits for auth-backend)
  6. Report ROADMAP_COMPLETE when ALL plans are done

Roadmap Architecture

New Epic-Hierarchy Model

Epic (optional parent)
  ├─ Roadmap 1
  │   ├─ Phase-Dev-Plan 1 (.claude/phase-plans/auth-backend/PROGRESS.json)
  │   ├─ Phase-Dev-Plan 2 (.claude/phase-plans/auth-frontend/PROGRESS.json)
  │   └─ Phase-Dev-Plan 3 (.claude/phase-plans/auth-testing/PROGRESS.json)
  └─ Roadmap 2
      ├─ Phase-Dev-Plan 4
      └─ Phase-Dev-Plan 5

Roadmap File Structure

Location: .claude/roadmaps/{roadmap-slug}/ROADMAP.json

{
  "roadmap_id": "uuid",
  "slug": "user-authentication",
  "title": "User Authentication System",
  "description": "Implement full authentication with JWT",
  "milestone": "v1.0",
  "status": "active",

  "parent_epic": {
    "epic_id": "uuid",
    "epic_slug": "auth-epic",
    "epic_path": ".claude/epics/auth-epic/EPIC.json"
  },

  "phase_dev_plan_refs": [
    {
      "slug": "auth-backend",
      "path": ".claude/phase-plans/auth-backend/PROGRESS.json",
      "title": "Authentication Backend",
      "status": "completed",
      "completion_percentage": 100,
      "created": "2026-02-04T...",
      "updated": "2026-02-04T..."
    },
    {
      "slug": "auth-frontend",
      "path": ".claude/phase-plans/auth-frontend/PROGRESS.json",
      "title": "Authentication Frontend",
      "status": "in_progress",
      "completion_percentage": 60,
      "created": "2026-02-04T...",
      "updated": "2026-02-04T..."
    },
    {
      "slug": "auth-testing",
      "path": ".claude/phase-plans/auth-testing/PROGRESS.json",
      "title": "Authentication E2E Testing",
      "status": "pending",
      "completion_percentage": 0,
      "created": "2026-02-04T...",
      "updated": "2026-02-04T..."
    }
  ],

  "cross_plan_dependencies": [
    {
      "dependent_slug": "auth-frontend",
      "depends_on_slug": "auth-backend",
      "reason": "Frontend needs backend API endpoints"
    },
    {
      "dependent_slug": "auth-testing",
      "depends_on_slug": "auth-frontend",
      "reason": "E2E tests require full UI flow"
    }
  ],

  "metadata": {
    "plan_count": 3,
    "overall_completion_percentage": 53
  }
}

Read the full file on GitHub · 523 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 523 lines · 37 tokens per session scan A c9afca732ff5

Subscribe to this mod's changes

roadmap-orchestrator is an agent published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 4,071 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

rca-debugger

Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…

sangrokjung/claude-forge · 118 tokens

cavecrew-reviewer

Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.

stevesolun/ctx · 75 tokens

systematic-debugger

Specialist for bugs that reproduce but whose root cause is unknown. Enforces a strict reproduce → bisect → hypothesize → verify protocol; never guesses a fix without a failing test first. Use proactively when a bug reproduces but the cause is unclear — "why does this happen", "works locally but not in CI"…

sangrokjung/claude-forge · 170 tokens

observability-engineer

OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…

travisjneuman/.claude · 82 tokens

go-expert

Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.

travisjneuman/.claude · 69 tokens

mobile-release-manager

App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…

travisjneuman/.claude · 77 tokens