Sections and tasks under docs/tasks/. Full CRUD from the dashboard or the CLI. Every task is a YAML file you can diff, review and blame: it really is one.
Roadmapped
The roadmap.md is dead.
All hail the task.yaml.
Transform your repo into your task management tool. Visualize your backlog, what’s finished, and what’s planned up ahead, and lead your development to success with a true big-picture view: a Monday/Jira/Linear-like live project management dashboard, running on the files your AI agent already writes.
Get started on GitHub →
agent prompt
Install Roadmapped in my repo: https://github.com/5e1y/roadmapped
There’s no step 2. We checked.
you › take the next task
agent › #14 Deploy to Cloudflare Pages → in_progress
$ npx wrangler deploy
agent › Live at roadmapped.dev. You’re on it.
agent › #14 done · record written
you › next
agent › #10 Embed the real dashboard in the homepage → in_progress
$ npx roadmapped start 10
agent › The window on the right? That’s it. Same app, not a replica.
agent › #10 stays in_progress until you stop looking.
Two windows, two jobs. On the left: the loop your agent runs on a ticket
(take it, do the work, record it). On the right: the real dashboard, not a
mockup. It’s the same app npx roadmapped dashboard opens on your
machine, loaded here with this page’s own backlog. Click around: the data
is real and the interactions work, only writes are blocked, so nothing you
click here ends up in our repo. Ticket #10, “Embed the real dashboard
in the homepage,” is marked in progress right on this page. Watch it
decide whether it’s done.
$ ls docs/tasks/
What’s in the folder
Priority is a temperature (0–100), not a stage rank: it rises with age and with how many other tasks it blocks, so next always hands your agent the thing that actually matters. done / available / locked states are computed live from the dependency graph, never stored. Nothing drifts out of sync, because there’s no second copy.
A CLI (npx roadmapped), a Claude skill, and an MCP server exposing the same commands as tools. Your agent creates specs, tasks and dependencies in the correct schema, and records what it ships with more discipline than most of us manage.
Every write (dashboard, CLI or MCP) goes through the same validator. On error, the change rolls back. Ids are never reused. Your git history is the audit log.
The dashboard updates itself the moment your agent writes: file-watch plus SSE, no refresh. The in-progress task pulses; a timestamped activity panel shows what changed and when.
The tool ships once; the data belongs to whichever repo you launch it from. Every dashboard header spells out which one it’s looking at (Roadmapped × your-repo), so two open windows never get confused for the same project.
A pre-commit hook refuses a commit that touches product files while nothing is in_progress. It chains after your existing hooks (husky, lefthook, whatever) instead of replacing them. --no-verify still works; skipping the ticket becomes a choice, not an accident.
The Docs view renders the markdown already in your docs/ folder (specs, notes, the guide). No copy, no export. A scratch notepad lives beside it for the thoughts that aren’t tasks yet. Same repo, same window as the backlog.
$ git diff docs/tasks/02-feature/17-dark-mode.yaml +status: done
How it works, start to finish
-
Point your agent at a rambling
roadmap.md, or just tell it what needs to happen. It turns that into traceable tickets: one YAML file per task, filed in the right type folder, dependencies wired up. -
The same CLI and Claude skill it used to create the ticket also take it, flip its status, and record what shipped when it’s done.
-
Every write is a file change in your repo. Reviewing a new ticket, a status flip or a finished task looks exactly like reviewing a pull request, because that is what it is.
-
Backlog, roadmap and activity, computed live from those same files the moment your agent writes. No second database to keep in sync, because there isn’t one.
Yes, it’s a folder of YAML files. No, it’s not a database. That’s kind of the point.
$ git log --oneline docs/tasks/
Built by using itself
Roadmapped’s own backlog is managed by Roadmapped, mostly by a Claude agent that records every task it ships. Nothing gets archived: a done task just stays done, right where it was, with its outcome, verification and commit written onto the file. The done backlog and the commit history are the changelog. If you want to know whether the workflow holds up, don’t take our word for it: read the backlog.
$ node -v v22.18.0
Quickstart
Claude Code plugin
Inside a Claude Code session; the agent handles the setup.
/plugin marketplace add 5e1y/roadmapped
/plugin install roadmapped@roadmapped
ornpm
npx roadmapped init
# scaffold docs/tasks/, the skill, the git guard
npm install
# activates the hooks + MCP
orStraight from GitHub
No npm registry involved.
npx --yes github:5e1y/roadmapped init
npm install
After install
Whichever door you came in: restart the session, then
npx roadmapped dashboard
# dashboard on http://localhost:5173
npx roadmapped --help
# the CLI your agent (or you) drives
Needs Node ≥ 22.18 and a package.json in the repo. The dashboard ships pre-built, so install pulls ~30 MB, not a front-end toolchain. All three roads end in the same wired state, and every install updates itself from GitHub in the background — installing is the last time you think about installing. Point your AI agent at the Claude skill (or just ask it to install Roadmapped from GitHub) and it takes it from there.
$ curl api.roadmapped.dev
curl: (6) Could not resolve host
Where your data lives
On your machine, in your repo. Not out of principle: we simply don’t have a server to send it to. Deleting your account is rm -rf. GDPR compliant by design; the design being that we never had your data.
$ head -1 LICENSE
MIT License
Free, and actually free
MIT licensed. No pricing page, no seats, no “contact sales.” We don’t have a customer success team to schedule an onboarding call. We don’t have customers. It’s free.
$ open https://github.com/5e1y/roadmapped
Still reading? That’s the whole pitch.
Point your agent at the repo, or hand it the prompt below, and it takes it from there.
Get started on GitHub →
agent prompt
Install Roadmapped in my repo: https://github.com/5e1y/roadmapped