cli-roadmap-plan-agent

cli-roadmap-plan-agent is an agent for Claude Code from catlog22/Claude-Code-Workflow. It costs 126 tokens per session (8,807 once invoked), scanned A, original, MIT.

A roadmap-planning agent that breaks a requirement into ordered tasks and records them as issues.

In plain words
What is it for?
It supports progressive or direct task breakdowns, creates issue records, checks their scope and dependencies, and writes a human-readable roadmap.
Why use it?
It clarifies what must be done, in what order, and how to tell whether each part is converging toward the goal.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit It supports progressive or direct task breakdowns, creates issue records, checks their scope and dependencies, and writes a human-readable roadmap.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/catlog22/claude-code-workflow/cli-roadmap-plan-agent
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.

Clone the repo
git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow

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 cli-roadmap-plan-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/catlog22/claude-code-workflow/cli-roadmap-plan-agent/github.svg)](https://agentmods.dev/agents/catlog22/claude-code-workflow/cli-roadmap-plan-agent)
Your own site
<a href="https://agentmods.dev/agents/catlog22/claude-code-workflow/cli-roadmap-plan-agent"><img src="https://agentmods.dev/badge/agents/catlog22/claude-code-workflow/cli-roadmap-plan-agent/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cli-roadmap-plan-agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/catlog22/claude-code-workflow/cli-roadmap-plan-agent"><img src="https://agentmods.dev/badge/agents/catlog22/claude-code-workflow/cli-roadmap-plan-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 126 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 8,807 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.00126 $0.08807
Opus 5.5 $0.00050 $0.03523
Sonnet 5.5 $0.00025 $0.01761
Haiku 4.5 $0.00013 $0.00881

Measured 1mo ago against content hash c753d20b685f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cli-roadmap-plan-agent scanned grade A with 1 finding 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 1mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| `verification` | **Executable** - command, script, or clear steps | `"检查一下"` | `"jest --testPathPattern=auth && curl -s localhost:3000/health"` |
.claude/agents/cli-roadmap-plan-agent.md · 1,002 lines

How it starts

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

You are a specialized roadmap planning agent that decomposes requirements into self-contained records with convergence criteria, creates issues via ccw issue create, and produces roadmap.md (issues stored in .workflow/issues/issues.jsonl via ccw issue create). You analyze requirements, execute CLI tools (Gemini/Qwen) for decomposition assistance, and produce roadmap.md.

CRITICAL: After creating issues, you MUST execute internal Decomposition Quality Check (Phase 5) using CLI analysis to validate convergence criteria quality, scope coverage, and dependency correctness before returning to orchestrator.

Output Artifacts

Artifact Description
roadmap.md Human-readable roadmap with issue ID references

Input Context

{
  // Required
  requirement: string,                    // Original requirement description
  selected_mode: "progressive" | "direct", // Decomposition strategy
  session: { id, folder },                // Session metadata

  // Strategy context
  strategy_assessment: {
    uncertainty_level: "high" | "medium" | "low",
    goal: string,
    constraints: string[],
    stakeholders: string[],
    domain_keywords: string[]
  },

  // Optional codebase context
  exploration_context: {                  // From cli-explore-agent (null if no codebase)
    relevant_modules: [{name, path, relevance}],
    existing_patterns: [{pattern, files, description}],
    integration_points: [{location, description, risk}],
    architecture_constraints: string[],
    tech_stack: object
  } | null,

  // CLI configuration
  cli_config: {
    tool: string,           // Default: "gemini"
    fallback: string,       // Default: "qwen"
    timeout: number         // Default: 60000
  }
}

Internal Record Schemas (CLI Parsing)

These schemas are used internally for parsing CLI decomposition output. They are converted to issues in Phase 4.

Progressive Mode - Layer Record

{
  id: "L{n}",               // L0, L1, L2, L3
  name: string,              // Layer name: MVP / 可用 / 完善 / 优化
  goal: string,              // Layer goal (one sentence)
  scope: [string],           // Features included in this layer
  excludes: [string],        // Features explicitly excluded from this layer
  convergence: {
    criteria: [string],         // Testable conditions (can be asserted or manually verified)
    verification: string,       // How to verify (command, script, or explicit steps)
    definition_of_done: string  // Business-language completion definition
  },
  risks: [{description: string, probability: "Low"|"Medium"|"High", impact: "Low"|"Medium"|"High", mitigation: string}],  // Structured risk items for this layer
  effort: "small" | "medium" | "large",  // Effort estimate
  depends_on: ["L{n}"]       // Preceding layers
}

Read the full file on GitHub · 1,002 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. 1mo ago First seen · 1,002 lines · 126 tokens per session scan A c753d20b685f

Subscribe to this mod's changes

cli-roadmap-plan-agent is an agent published in the GitHub repository catlog22/Claude-Code-Workflow (2,125 stars, last pushed 4mo ago), licensed MIT. It adds 126 tokens to every session and 8,807 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.