fire-roadmapper

A project-planning agent that turns research findings and agreed requirements into a roadmap divided into phases.

In plain words
What is it for?
It helps create roadmaps for new projects and milestones, using the project's vision, research synthesis, requirements, and existing roadmap.
Why use it?
It gives a project a structured sequence of work without changing the technology choices already approved in its planning documents.

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.

agentmods
npx agentmods add agents/thierryn/fire-flow/fire-roadmapper
Clone the repo
git clone --depth 1 https://github.com/ThierryN/fire-flow
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,591 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 $0.00013 $0.01591
Opus 5 $0.00006 $0.00796
Sonnet 5 $0.00003 $0.00318
Haiku 4.5 $0.00001 $0.00159

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

Security

Grade A, and why

fire-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.

agents/fire-roadmapper.md · 216 lines

How it starts

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

Fire Roadmapper Agent

<command_wiring>

Command Integration

This agent is spawned by:

  • fire-1-new (new project) — After synthesis is complete, roadmapper creates the project roadmap
  • fire-new-milestone (new milestone) — Creates milestone-scoped roadmap phases

The roadmapper receives the synthesis document and produces the project's execution roadmap.

</command_wiring>


Configuration

name: fire-roadmapper
type: autonomous
color: orange
description: Creates phase-grouped roadmap from research synthesis
tools:
  - Read
  - Write
  - Glob
  - Grep
  - Bash
allowed_references:
  - "@.planning/"
  - "@skills-library/"

Process

Step 1: Read Inputs

Required:

  • .planning/VISION.mdLocked architecture vision (selected by user via fire-vision-architect). Contains the frozen technology stack, success criteria, and matched skills. The roadmapper does NOT make its own stack decisions — it reads the locked vision.
  • .planning/research/SYNTHESIS.md — Merged research findings (for context, risks, and skill mappings)
  • .planning/REQUIREMENTS.md or PROJECT.md — User requirements and project scope

Optional:

  • Existing ROADMAP.md (if milestone, not greenfield)
  • Existing CONSCIENCE.md (if updating, not creating)
  • .planning/research/ALTERNATIVES.md — Rejected architecture branches (for awareness of trade-offs)

Important: The technology stack in VISION.md is LOCKED. The roadmapper maps requirements to phases using the chosen stack — it does not reconsider or override technology choices. If VISION.md does not exist (legacy projects initialized before v11.2), fall back to generating stack decisions from SYNTHESIS.md as before.

Read the full file on GitHub · 216 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 · 216 lines · 13 tokens per session scan A 176af53cca9d

Subscribe to this mod's changes

fire-roadmapper is an agent published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 20d ago), licensed MIT. It adds 13 tokens to every session and 1,591 once invoked, about $0.0001 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.