โ† ClaudeAtlas

roadmap-add-tasklisted

{{ ๐›€๐›€๐›€ }} Add a task to a rich-format project roadmap with correct ID, dependency wiring, and graph integrity โ€” ID assignment, status computation, dependency edges in both directions, and no unconnected islands.
JasonWarrenUK/goblin-mode ยท โ˜… 5 ยท AI & Automation ยท score 73
Install: claude install-skill JasonWarrenUK/goblin-mode
# Roadmap Task Adder Adds a well-formed task to an existing rich-format roadmap. The job is not appending a line โ€” it is placing the task correctly in the dependency graph, wiring its relationships in **both** artefacts (`.claude/roadmaps.json` and the PHASE file it names), and leaving the roadmap coherent. Shared conventions: `~/.claude/library/references/roadmap-conventions.md`. The CLI is `python3 "$HOME"/.claude/library/scripts/roadmap.py`. --- ## Step 1 โ€” Locate the roadmap and check the format Run `python3 "$HOME"/.claude/library/scripts/roadmap.py detect`. Exit **3** = old simple format โ€” **stop and tell the user to run `roadmap-migrate` first**. Exit **2** = could not locate/parse โ€” ask the user for the path. Only proceed on exit 0. Read the full `roadmaps.json` and the active phase's PHASE file before adding โ€” you need the existing task graph, milestone IDs, gates, and categories. --- ## Step 2 โ€” Understand what to add Extract: **description**; **milestone** (which milestone โ€” ask if unclear); **category** (2โ€“3 letter prefix, reuse an existing one in that milestone where it fits); **dependencies** (what must be done first; what it unblocks); **assignee** (ask the user directly โ€” never infer it from the description, the git author, the category owner, or who is running this skill; leave it unset if the user doesn't say). Ask before proceeding if any is ambiguous โ€” a badly placed task is worse than a delayed one. --- ## Step 3 โ€” Assign a task ID `{Milestone