← ClaudeAtlas

roadmappedlisted

Roadmapped project management — use BEFORE modifying any file in this repo, whatever the framing �� feature, feedback, rework, post-done fix, "ASAP" included — and whenever work must be created, planned, executed, or logged (tasks, specs, roadmaps, documentation), when the user says "let's work through the roadmap", "create the tasks", "fix this", or on the FIRST use in a repo (mandatory setup phase).
5e1y/roadmapped · ★ 7 · Data & Documents · score 73
Install: claude install-skill 5e1y/roadmapped
# Roadmapped — the file-driven project ## Compass Flat YAML/markdown files under `docs/tasks/` are the ONLY source of truth (no parallel plan). 9 fixed, immutable TYPES (`01-bug` → `09-business` = the NATURE of the work, one dashboard column each — never a "when", never a team). Priority is a computed TEMPERATURE, not a stage rank and not an epic order (epics are unordered groupings). The `npx roadmapped <command>` CLI — installable via npm, GitHub (`github:5e1y/roadmapped`), or the Claude Code plugin — or the roadmapped MCP tools if loaded (same core, same guarantees) — is your ONLY write interface — never hand-edit a YAML the CLI covers. (In the Roadmapped repo itself, `node scripts/task.mjs <command>` remains equivalent.) ## Decision ladder — stop at the first matching row **Every repo change = one roadmapped unit, no exceptions.** `done` is a boundary, not a lid (a rework/review-fix gets its own unit); "ASAP" is never a reason to skip it — logging IS the fast path (~2 commands). Only artefact-free exchange (question, explanation, status) stays conversational. **Before creating anything, check it isn't already tracked**: one `list --type <t> --status todo` (or `next --type <t>`) — a self-contained call (allowed below), NOT a priority recompute (forbidden); don't conflate the two uses of "reading the backlog". | The work is… | do this — do NOT default to a fresh isolated ticket | |---|---| | doesn't deserve to exist | nothing | | a note/change on an **existing** ticket