What is shipkit-spec-roadmap?

A roadmap skill that decides which feature specifications to write first. It scores features using product goals, dependencies, foundational value, and implementation complexity.

Use it after product and engineering definitions are available. It creates a machine-readable roadmap for planning the order of specification work.

It turns a backlog of possible specifications into an ordered sequence, so foundational or high-priority work is handled first.

shipkit-spec-roadmap — Skill by stefan-stepzero

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/stefan-stepzero/shipkit/shipkit-spec-roadmap

Any agent

npx skills add stefan-stepzero/shipkit --skill shipkit-spec-roadmap

Clone the repo

git clone --depth 1 https://github.com/stefan-stepzero/shipkit

Made for: Claude Code, Codex.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00041	$0.02693
Opus 5	$0.00020	$0.01347
Sonnet 5	$0.00008	$0.00539
Haiku 4.5	$0.00004	$0.00269

Measured 2d ago against content hash bff8df566d4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

shipkit-spec-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 2d 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.

install/skills/shipkit-spec-roadmap/SKILL.md · 297 lines

How it starts

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

shipkit-spec-roadmap — Spec Prioritization Roadmap

Purpose: Bridge the gap between definitions and specs by building an explicit prioritization roadmap. Scores features by goal-gate phasing, dependency depth, foundation value, and mechanism complexity to determine spec order.

Output format: JSON — structured roadmap at .shipkit/spec-roadmap.json

When to Invoke

User triggers:

"What should I spec first?"
"Prioritize the features"
"Create a spec roadmap"
"Spec backlog"
"What order should I write specs?"

Before:

/shipkit-spec (this determines WHICH spec to write next)

After:

/shipkit-product-definition (need features to prioritize)
/shipkit-engineering-definition (need mechanisms for effort estimation)
/shipkit-product-goals (recommended — gates drive phasing)

Workflow position:

After definitions are complete, before writing individual specs
Can be re-run after new features are added or priorities change

Prerequisites

Required:

.shipkit/product-definition.json — features to prioritize
.shipkit/engineering-definition.json — mechanisms for effort estimation

Recommended:

.shipkit/goals/*.json — gate definitions for phase mapping (especially goals/strategic.json or goals/product.json)

Optional:

.shipkit/specs/ — detect already-specced features to mark as completed

If goals missing: Fall back to single-phase roadmap sorted by dependency + foundation value only.

Arguments

If $ARGUMENTS contains --update: Load existing spec-roadmap.json, refresh spec statuses, re-score, and present changes.

If $ARGUMENTS contains --regenerate: Discard existing roadmap and rebuild from scratch.

If $ARGUMENTS is empty: Check for existing file and offer choices.

Process

Step 0: Check Existing Roadmap

Fork context — no user prompts. You are dispatched in a fork and have no user channel. Skip the file-exists menu entirely.

Read .shipkit/spec-roadmap.json (if exists)
If $ARGUMENTS contains --update: proceed to Step 1 with existing data as baseline
If $ARGUMENTS contains --regenerate or no file exists: proceed to Step 1 fresh
If file exists and no argument: read .shipkit/reviews/planning-assessment.json if present. If the latest review lists a gap against this artifact, archive the existing file to .shipkit/.archive/spec-roadmap.YYYY-MM-DD.json and regenerate addressing the gap. Otherwise, read the existing file and exit early with a "no changes needed" report — the reviewer already accepted it.

Read the full file on GitHub · 297 lines

Files

What ships with it

2 files 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.

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.

2d ago First seen · 297 lines · 41 tokens per session scan A bff8df566d4b

Subscribe to this mod's changes

shipkit-spec-roadmap is a skill published in the GitHub repository stefan-stepzero/shipkit (1 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 2,693 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.

Planning ai-tools anthropic claude claude-code claude-skills developer-tools

opencli-sitemap-author

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener/OpenCLI · 67 tokens

omh-buzz

This is a Hermes-native buzz workflow skill.

rlaope/oh-my-hermes · 95 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 tokens

redteam-api-detail-pack

Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.

Netw0rkNoob/VulnClaw · 61 tokens

redteam-postex-detail-pack

Domain routing and boundary guidance for authorized post-exploitation testing after initial access, including privilege escalation, persistence, lateral movement, data collection, and cleanup considerations. Use when a task belongs to the post-exploitation domain and needs scope, evidence, pivot, or exit criteria.