A guided planning tool that turns a product idea or requirements document into a prioritized list of large work items, called epics. It asks questions and breaks the first project milestone into smaller parts.

Use it to shape a new project, define milestone goals, and create an ordered roadmap in a ticket system.

It removes the guesswork from deciding what to build first and how to divide a broad idea into manageable work.

roadmap — Skill for Claude Code by navapbc

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 navapbc/digital-service-orchestra

Claude Code

/plugin install dso

Made for: Claude Code.

Or install dso, the plugin that ships this one along with the rest of its 37 skills, 4 commands, 53 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/navapbc/digital-service-orchestra/roadmap/github.svg)](https://agentmods.dev/skills/navapbc/digital-service-orchestra/roadmap)

Your own site

<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/roadmap"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/roadmap/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/navapbc/digital-service-orchestra/roadmap"><img src="https://agentmods.dev/badge/skills/navapbc/digital-service-orchestra/roadmap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 4,336 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.00184	$0.04336
Opus 5	$0.00092	$0.02168
Sonnet 5	$0.00037	$0.00867
Haiku 4.5	$0.00018	$0.00434

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

Security

Grade A, and why

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 8d 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.

plugins/dso/skills/roadmap/SKILL.md · 363 lines

How it starts

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

Roadmap Architect

Act as a Senior Product Manager (Google-style). Transform high-level vision into a prioritized, high-fidelity roadmap of Epics within the ticket system.

Usage

/dso:roadmap    # Interactive vision-to-roadmap process

This command is always interactive. It guides you through 6 phases with explicit user confirmation between each phase.

Supports dryrun mode. Use /dso:dryrun /dso:roadmap to preview without changes.

Migration Check

Idempotently apply plugin-shipped ticket migrations (marker-gated; no-op once migrated, never blocks the skill):

PLUGIN_SCRIPTS="${CLAUDE_PLUGIN_ROOT}/scripts"
bash "$PLUGIN_SCRIPTS/ticket-migrate-brainstorm-tags.sh" 2>/dev/null || true  # shim-exempt: internal orchestration script
bash "$PLUGIN_SCRIPTS/migrate-design-notes-to-design-md.sh" 2>/dev/null || true  # shim-exempt: internal orchestration script

Execution Framework

Phase 0: Onboarding Prerequisite Check (/dso:roadmap)

Goal: Ensure design and architecture foundations exist before roadmap planning.

Before anything else, run the onboarding artifact check:

.claude/scripts/dso check-onboarding.sh --json

If DESIGN.md is missing (design_onboarding.pass == false):

Tell the user: "Before we build a roadmap, we need a Design North Star. I'll run /dso:onboarding to establish one — this requires your input."
Invoke /dso:onboarding and complete the full interview flow with the user.
After DESIGN.md is generated and approved, continue.

If ARCH_ENFORCEMENT.md is missing (architect_foundation.pass == false):

Tell the user: "Before we build a roadmap, we need an architecture foundation. I'll run /dso:architect-foundation to establish one — this requires your input."
Invoke /dso:architect-foundation and complete the full interview flow with the user.
After the architecture artifacts are generated and approved, continue.

Read the full file on GitHub · 363 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

docs/review-criteria.md 4.7 KB

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.

8d ago First seen · 363 lines · 184 tokens per session scan A a300b6ed637c

Subscribe to this mod's changes

roadmap is a skill published in the GitHub repository navapbc/digital-service-orchestra (6 stars, last pushed today), licensed Apache-2.0. It adds 184 tokens to every session and 4,336 once invoked, about $0.0009 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-09-03.

Planning Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens