live
< 7d
< 30d
older
stale
A JSON-driven map of every package, flow, and milestone in your
project — generated from git and surfaced as a
~3k-token atlas.md, so cold Claude Code sessions land
oriented instead of burning 80k on rediscovery.
> /plugin marketplace add RobotRegistryFoundation/claude-code-plugins > /plugin install workflow-atlas@robotregistryfoundation
Without a map, Claude greps your repo from scratch — package layout, which files matter, what's in flight. That's tens of thousands of tokens spent re-learning the same shape of the same project. The atlas turns it into a one-time read.
nodes.json + flows.json — the package map and named flows through it. The map of what matters.refresh, the generator derives sprints.json, activity.json, atlas.md, badge.svg from git log and your Claude session logs./workflow-atlas init writes a section that points Claude to atlas.md first. Cold sessions skip rediscovery — the math is operationally provable.
Atlas is a single-page app served from workflowatlas.cc. Each
tab is a different lens on the same five JSON files in your repo.
Click through — they all work locally and via ?atlas=<url> permalinks.
The atlas isn't just a webpage — the same JSON shows up in your terminal, on every PR, in your README, and in AI-readable markdown. Wherever a teammate or a model looks, they see the same shape of the project.
Plus PR comments and a README badge — both auto-updated from the same JSON.
/workflow-atlas review
prints the last sprint to stdout — tokens, tasks, cache rate.
3k-token markdown the next cold Claude session reads first. Loop closed.
Atlas, Sprint Log, Forecast, Kanban, Usage, Backlog — view-only for reviewers.
Copy sprint-summary.yml into .github/workflows/ — every PR push updates a comment with the atlas summary. Reviewers get the mental model for free.
Drop  — shows flow count, milestones, recent cache hit rate. Embeddable everywhere.
Plugin host handles updates across CLI, IDE extensions, and desktop.
/plugin marketplace add \ RobotRegistryFoundation/claude-code-plugins /plugin install \ workflow-atlas@robotregistryfoundation
Self-managed. You own git pull for updates.
git clone \ https://github.com/craigm26/\ workflow-atlas \ ~/.claude/plugins/workflow-atlas
Submission to anthropics/claude-plugins-official is open.
/plugin install \ workflow-atlas@\ claude-plugins-official
/workflow-atlas initScaffold docs/workflows/ + register in CLAUDE.md/workflow-atlas refreshRe-derive sprints, activity, atlas.md, badge.svg from git/workflow-atlas openOpen the local atlas in the browser/workflow-atlas add-flowAuthor a new flow interactively/workflow-atlas reviewPrint the last sprint to your terminal/workflow-atlas hand-off ‹flow›#‹step›Print a claude:// deeplink for a step/workflow-atlas diff ‹sha1›..‹sha2›Atlas-terms diff — which nodes + flows changed/workflow-atlas install-hookDrop a pre-push hook that auto-refreshes/workflow-atlas spawn-pendingSpawn a Claude session from a pending hand-off/workflow-atlas note ‹sprint› "‹text›"Append a sprint commentary entrydocs/workflows → examples/ symlink from a v0.9.0 smoke test removed./workflow-atlas diff ‹sha1›..‹sha2› + PR overlay (?diff=…), JSON Schemas at schemas/, animated demo GIF generator.install-hook for pre-push auto-refresh.review, hand-off, atlas.md + badge.svg, GitHub Action template.claude:// deeplink./usage — 5h window, cache hit, effective tokens/commit, rediscovery savings.Try the actual app on real data. No install needed — these are permalinks to the workflowatlas.cc renderer pointed at JSON in the repo.
Five flows describing how the plugin works. Try the Usage and Kanban tabs — drag a card to "In progress" and pick "Claude" to see the hand-off dialog. Forecast shows the v0.2.0 → v0.7.0 burn-down.
A real Flutter + Nexa SDK NPU project with Parakeet / LFM2 / OmniNeural models. Click "Real-time caption pipeline" to trace audio mic → NPU → AR display.
Both atlases loaded together. Each repo becomes its own family container; node ids namespaced as <repo-slug>:<id> so cross-repo flow steps work naturally.
?activity=on&since=7d permalink. Nodes touched in the last week glow orange; everything else fades to 15%. The "what's Claude been doing?" view.
?atlas=<base-url> for one repo,
?atlas=<base1>;<base2>;… for many.
A base is any directory that serves nodes.json, flows.json, sprints.json, milestones.json, and optionally claude-md.json + memory-refs.json.