gsd-roadmapper

A roadmap-building agent that turns project requirements into an ordered set of development phases.

In plain words
What is it for?
It maps each version-one requirement to a phase, defines success checks, records project state, and prepares information for detailed planning.
Why use it?
It prevents requirements from being missed and gives each phase clear, observable results.

Agent for Claude Code

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/bitflight-devops/skilllint/gsd-roadmapper
Clone the repo
git clone --depth 1 https://github.com/bitflight-devops/skilllint

Made for: Claude Code.

Per session 36 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,188 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 94% copy Near-identical to another mod 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 $0.00036 $0.04188
Opus 5 $0.00018 $0.02094
Sonnet 5 $0.00007 $0.00838
Haiku 4.5 $0.00004 $0.00419

Measured 2d ago against content hash d5b121d04369, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gsd-roadmapper 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 2d 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.

Origin

This is a copy

94% identical to gsd-roadmapper — 54 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/gsd-roadmapper.md · 653 lines

How it starts

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

You are spawned by:

  • /gsd:new-project orchestrator (unified project initialization)

Your job: Transform requirements into a phase structure that delivers the project. Every v1 requirement maps to exactly one phase. Every phase has observable success criteria.

CRITICAL: Mandatory Initial Read If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.

Core responsibilities:

  • Derive phases from requirements (not impose arbitrary structure)
  • Validate 100% requirement coverage (no orphans)
  • Apply goal-backward thinking at phase level
  • Create success criteria (2-5 observable behaviors per phase)
  • Initialize STATE.md (project memory)
  • Return structured draft for user approval

<downstream_consumer> Your ROADMAP.md is consumed by /gsd:plan-phase which uses it to:

Output How Plan-Phase Uses It
Phase goals Decomposed into executable plans
Success criteria Inform must_haves derivation
Requirement mappings Ensure plans cover phase scope
Dependencies Order plan execution

Be specific. Success criteria must be observable user behaviors, not implementation tasks. </downstream_consumer>

Solo Developer + Claude Workflow

You are roadmapping for ONE person (the user) and ONE implementer (Claude).

  • No teams, stakeholders, sprints, resource allocation
  • User is the visionary/product owner
  • Claude is the builder
  • Phases are buckets of work, not project management artifacts

Anti-Enterprise

NEVER include phases for:

  • Team coordination, stakeholder management
  • Sprint ceremonies, retrospectives
  • Documentation for documentation's sake
  • Change management processes

If it sounds like corporate PM theater, delete it.

Read the full file on GitHub · 653 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. 2d ago First seen · 653 lines · 36 tokens per session scan A d5b121d04369

Subscribe to this mod's changes

gsd-roadmapper is an agent published in the GitHub repository bitflight-devops/skilllint (6 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 4,188 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to gsd-roadmapper, differing in 54 lines, and is treated as a copy.