roadmap-digest
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Generate a self-contained, human-digestible HTML view of a project's roadmap and what has been completed — a companion that runs IN PARALLEL to the roadmap file: it never edits the roadmap, and it is regenerated to a stable path so `git diff` shows how the human-facing picture drifts as the plan evolves. Reads roadmap/plan files for intent and cross-references journal/ + git history for what actually shipped, then renders an at-a-glance dashboard (overall progress ring, status-colored phase cards, recently-shipped and next-up strips). Use this whenever the user wants to "see the roadmap", "show progress", "what's done vs what's left", a "status page or dashboard for the plan", a "roadmap summary for the team", or to turn a dense ROADMAP.md / plan/ folder into something scannable in fifteen seconds — even if they never say the word "HTML". This is deliberately distinct from three sibling skills: it is NOT explaining a single decision or finding to an audience (use `explainer`), NOT a backward-looking recap of what the assistant just did (use `audit-trail`), and NOT a forward design proposal or RFC (use `forward-spec`). Reach for roadmap-digest specifically when the subject is the whole roadmap plus its completion state, packaged for rapid human digestion.
In this repository7 other files it gives its agents.
- adversarialSkill
- audit-trailSkill
- codex-pairSkill
- explainerSkill
- forward-specSkill
- remarkable-htmlSkill
- remarkable-mdSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.