A skill for turning a large initiative into a phase-based roadmap of smaller development tasks saved as Markdown files.

Use it to record initiatives involving several tasks, dependencies, or more than a few steps in a structured roadmap under the workspace's task directory.

It gives multi-step work a clear backlog with phases and dependencies, so tasks can be picked up in an understandable order.

to-roadmap — Skill for Claude Code by SpaiR

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add SpaiR/task-pipeline

Claude Code

/plugin install task

Made for: Claude Code.

Or install task, the plugin that ships this one along with the rest of its 8 skills, 8 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/spair/task-pipeline/to-roadmap.svg)](https://agentmods.dev/skills/spair/task-pipeline/to-roadmap)

Your own site

<a href="https://agentmods.dev/skills/spair/task-pipeline/to-roadmap"><img src="https://agentmods.dev/badge/skills/spair/task-pipeline/to-roadmap.svg" alt="Measured on agentmods" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,172 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.04172
Opus 5	$0.00017	$0.02086
Sonnet 5	$0.00007	$0.00834
Haiku 4.5	$0.00003	$0.00417

Measured 7d ago against content hash 8d582f8bded4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

to-roadmap scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/to-roadmap/SKILL.md · 194 lines

How it starts

The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix a multi-task initiative (phases, dependencies, or more than a couple of atomic steps) into .task/roadmap/<slug>.md. Multi-task counterpart to /task:to-task / /task:to-plan (which each fix one task). Depth is fixed: one roadmap file, flag-free.

Input: $ARGUMENTS — a rough description of the initiative, or a reference back to a prior discussion in this conversation ("build a roadmap from what we discussed").

Format contract: docs/contract.md § Roadmap file format is the single source of truth for the output structure. This file describes the authoring flow that produces it.

Instructions

Step 0: Setup gate

Resolve the pipeline root, then check whether its CLAUDE.md exists:

source "${CLAUDE_PLUGIN_ROOT}/skills/_lib/resolve-ws.sh"   # exports AI_DIR
echo "$AI_DIR"                                             # the resolved root — use this value verbatim in every artifact path below
[[ -f "$AI_DIR/CLAUDE.md" ]] || echo "CLAUDE.md not found"

Every artifact path in this skill is under that resolved $AI_DIR, never the cwd — .task/roadmap/<slug>.md below is shorthand for $AI_DIR/roadmap/<slug>.md. A cwd-relative write from a subdirectory or a linked worktree would create a second .task/ that validate.sh (which resolves $AI_DIR itself) never sees.

CLAUDE.md not found → /task:to-roadmap is intake-capable: read ${CLAUDE_PLUGIN_ROOT}/skills/_lib/setup.md and follow it (detect stack → write $AI_DIR/CLAUDE.md from its template → record git config --local task.root → exclude .task → report what was written), then continue. No confirmation chip — the file is written first and edited afterwards if a detected value was wrong. setup.md owns the sub-steps and the template; do not restate either here. If .task/CLAUDE.md already exists, leave it untouched: it is user-owned, and only task.root and the .git/info/exclude line are restored when missing.

Read the full file on GitHub · 194 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago First seen · 194 lines · 34 tokens per session scan A 8d582f8bded4

Subscribe to this mod's changes

to-roadmap is a skill published in the GitHub repository SpaiR/task-pipeline (7 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 4,172 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Planning Project management ai-agents claude-code-plugin developer-tools workflow

batch

Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.

mikestankavich/claude-ship-workflow · 31 tokens

prep

Spec a ticket before it is dispatched. Brainstorms it, decides everything it can recommend an answer for, asks a present human about the little that survives, and leaves the spec, the decisions and anything still open as one ticket comment. No worktree, no branch, no pull request, and the ticket stays where it was.

mikestankavich/claude-ship-workflow · 68 tokens

work

Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it. Use when asked to work a ticket end-to-end.

mikestankavich/claude-ship-workflow · 53 tokens

daily-working

End-to-end pipeline: pull a task from Redmine by ID, sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension (claude-in-chrome), and keep the Redmine ticket in sync throughout (in-progress…

tms-tungnguyen3/daily_working · 81 tokens

web-drift

Use for the live-website agent-readiness audit, "run the web-drift loop", "audit our websites", "are our sites still readable by an agent", "web drift sweep", "check the public sites", or a scheduled site-audit cadence run. Enumerates every site the consumer declared in WEBDRIFTSITES, probes each over read-only HTTP…

dwarvesf/dwarves-kit · 230 tokens

shipyard-executing-plans

Use when you have a written implementation plan to execute, either in the current session with builder/reviewer agents or in a separate session with review checkpoints. Also use when the user says "build this", "implement this", "execute the plan", "run the plan", or when a plan file has been loaded with independent…

lgbarn/shipyard · 78 tokens