open source · github template

No code.
No database.
Just roadmap.

Use the template, open Claude Code, and you have a roadmap assistant in your terminal. Tell it what's shipping, what changed, what needs a slide. It handles the structure. Git keeps the record. No seats. No renewals.

Claude Code — roadmap/
# You open the repo in Claude Code and say:

you We decided this morning to add offline mode to the mobile app. Ben's leading it, targeting summer.

claude Added to the mobile roadmap under Ben, targeted for summer.
Committed: feat(roadmap): add offline mode to mobile [agent]

you Can you put together a slide summarising everything we're shipping this summer?

claude Written to outputs/2026-03/summer-shipping-slide.html
Committed: feat(outputs): summer shipping slide [agent]

you What's Ben working on across the whole roadmap?

Why pay twice?
You already have the stack.

Every roadmap tool took your data, wrapped it in proprietary software, and charged you rent to see it. Per seat. Per month. Forever.

Clawmapper is a GitHub template that wires together tools you already use. Your roadmap lives as plain Markdown in the same place as your code — same version history, same access controls, same PR workflow. Claude handles the structure so you don't have to.

Cancel the roadmap tool. Nothing is lost.

Linear runs your execution. Clawmapper is the layer above.

Traditional tool
You
click through a UI
App
reads/writes DB
Your data
locked in vendor DB
With Clawmapper
You
talk to Claude
Claude
writes Markdown
Your data
plain files in Git

Three steps.
Then just talk.

01 /

Use the template

Use clawmapper/clawmapper on GitHub to create your own copy. The repo includes a pre-configured structure for roadmaps, outputs, context, and memory — along with the instructions that tell Claude how to behave.

02 /

Open it in Claude Code

Run claude in the repo directory. Claude reads your setup automatically — the conventions, who owns what, what's already in the roadmap.

03 /

Start talking

Describe an initiative, paste in meeting notes, ask for a status summary, or request a board-ready slide. Claude writes the roadmap files and commits the changes. Everything is versioned.

Every stakeholder.
One roadmap.

One repo. Ask for whatever view you need — Claude generates it. Nobody's waiting on a deck.

Generated from roadmap/ftl-drive.md · FTL Drive · Q2 2026
ItemStatusOwnerPriorityNotes
Warp coil calibrationShippedBenP1±0.003% variance, within spec
Exotic matter procurementIn progressClaudeP1Supplier confirmed, delivery Q2
Causality violation patchIn progressPlatformP1Regression in timeline branch
Passenger safety reviewPlannedBenP2Blocked on causality patch
Paradox resolution strategyDiscoveryTBDP1No consensus on approach yet
Grandfather clause complianceDiscoveryLegalP2Flagged by compliance, Q3 target
Mars route optimisationIn progressBenP1Pathfinding algo 60% complete
Relativistic UI latencyPlannedPlatformP2Time dilation UX unresolved
Heat death ETA dashboardPlannedClaudeP2Scope TBD
Multiverse A/B testingPlannedTBDP3Requires stable paradox infra first

Everything you already use.
Nothing you don't.

🐙
Substrate

GitHub

Version history, access control, pull request reviews, and collaboration — for free, with tooling every engineer already knows.

📄
Data layer

Markdown

Human-readable, diff-friendly, and permanent. Your roadmap is never trapped in a binary format or a proprietary schema.

Interface

Claude Code

The AI reads your repo, writes structured entries, generates artifacts, and commits changes — all from a conversation in your terminal.

For builders,
not bureaucracies.

As AI takes over more execution, the person planning the work is increasingly the person building it. Heavyweight roadmap tools weren't designed for this.

Founder-engineers

Track your own roadmap in the same GitHub account where you push code. No switching tabs, no separate tool, no extra login.

Small eng teams

Get structured roadmap management without paying for another SaaS seat. The "PM" is shared and always available.

PMs who live in Git

Stop maintaining roadmaps in tools that can't be reviewed, diffed, or rolled back. Your roadmap should have a git history.

Agencies & consultants

Clone a fresh repo per client. Each one is isolated, customisable, and hand-offable — with the full history intact.

This isn't just
a roadmap tool.

Clawmapper is one instance of a more general pattern. Once you see it, you can't unsee it.

The pattern is: text as data, Git as substrate, Claude Code as interface. The AI is the sole author of structured content. You provide the intent. It maintains the system.

Swap out roadmap files for research notes, life goals, a consulting engagement log, or a personal knowledge base — the architecture is identical. Clawmapper is the proof of concept. What you build next is up to you.

This repo
Product roadmaps
Initiatives, owners, quarters, output artifacts — all in Markdown, authored by Claude.
Use & adapt
Research repositories
Literature notes, experiment logs, hypothesis tracking. Claude maintains structure as the work evolves.
Use & adapt
Life & goals planning
Annual priorities, projects, weekly reviews. Private repo, same model — AI writes, Git remembers.
Use & adapt
Client engagements
One repo per client. Decisions log, deliverables tracker, meeting notes — all versioned and hand-offable.

Your roadmap, in a repo,
in five minutes.

Use the template, open Claude Code, and start talking. That's the whole setup.

gh repo create my-roadmap --template clawmapper/clawmapper

Requires GitHub CLI and Claude Code


View on GitHub ↗