Artefact roadmap
Three goblins in a trenchcoat pretending to be a senior developer. Claude Code config shaped by ADHD, friction, and spite.
npx -y skills add JasonWarrenUK/goblin-mode --skill artefact-roadmapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
{{ π«π«π« }} Generate the HTML roadmap dashboard deterministically via roadmap.py render.
SKILL.md
2.6 KB, as published. Nobody here has run it
Render the interactive roadmap dashboard. The HTML is generated deterministically by roadmap.py render from the template at ~/.claude/library/templates/roadmap-artefact.html β this skill runs the command and opens the result; it writes no HTML itself. Same data in, same file out, so regenerated artefacts diff cleanly and can never drift from roadmaps.json.
Shared conventions (statuses, colour table): ~/.claude/library/references/roadmap-conventions.md.
Steps
- Check the format. Run
python3 "$HOME"/.claude/library/scripts/roadmap.py detect. Exit 3 = old simple format β stop and tell the user to runroadmap-migratefirst. Exit 2 = could not locate/parse β ask for the path. Proceed on exit 0. - Render. Run
python3 "$HOME"/.claude/library/scripts/roadmap.py render, adding--phase "$ARGUMENTS"when the user named a phase (required if several are active). Default output:{project_root}/docs/artefacts/roadmap-{slug}.html. On a validation-discrepancy note in the output, still render (the page shows a discrepancy banner) but include the discrepancies in your report. - Open and report.
openthe written file. Report: the file path; milestone and task counts plus done percentage (roadmap.py stats); the unblockedtodotasks (roadmap.py readyβ surfaced directly, no need to open the file); any validation discrepancies.
Notes
- The dashboard refreshes automatically when
roadmap-maintainruns (recompute --render); invoke this skill for the first render or an on-demand refresh. - Sections, palette and behaviour live in the template. To change the dashboard's look, edit
library/templates/roadmap-artefact.html; to change status colours, change the canonical table (STATUS_STYLEinroadmap.py+ the conventions reference) β never patch a generated file. - The artefact is generated in the CLI's own canonical form (tabs, single-line JSON payload), not Prettier's. A repo that runs Prettier (or another formatter) in a pre-commit hook or CI should exclude it β add
docs/artefacts/roadmap-*.htmlto.prettierignore, the same way.claude/roadmaps.jsonis already excluded β so regenerating the dashboard never fights the formatter.