ship-roadmap

ship-roadmap is a skill for Claude Code, Codex from gtrabanco/agentic-workflow. It costs 59 tokens per session (1,735 once invoked), scanned A, original, MIT.

A staged roadmap workflow for planning, implementing, reviewing, and shipping one project unit at a time, usually through a human-reviewed pull request.

In plain words
What is it for?
Use it to advance a roadmap stage, run the related implementation and review work, handle existing issues after the roadmap, and report remaining proposals.
Why use it?
It gives long-running project work a repeatable progression and keeps merges and other hard-to-reverse decisions under the defined approval rules.

Skill for Claude CodeCodex

Part of the agentic-workflow plugin — 35 skills shipped together

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/gtrabanco/agentic-workflow/ship-roadmap
Any agent
npx skills add gtrabanco/agentic-workflow --skill ship-roadmap
Clone the repo
git clone --depth 1 https://github.com/gtrabanco/agentic-workflow

Made for: Claude Code, Codex.

Or install agentic-workflow, the plugin that ships this one along with the rest of its 35 skills.

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.

agentmods badge for ship-roadmap

README.md
[![agentmods](https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/ship-roadmap.svg)](https://agentmods.dev/skills/gtrabanco/agentic-workflow/ship-roadmap)
Your own site
<a href="https://agentmods.dev/skills/gtrabanco/agentic-workflow/ship-roadmap"><img src="https://agentmods.dev/badge/skills/gtrabanco/agentic-workflow/ship-roadmap.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,735 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.

ModelPer sessionOnce invoked
Fable 5 $0.00059 $0.01735
Opus 5 $0.00030 $0.00868
Sonnet 5 $0.00012 $0.00347
Haiku 4.5 $0.00006 $0.00173

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

Security

Grade A, and why

ship-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 today.

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.

packages/pi-agentic-workflow/skills/ship-roadmap/SKILL.md · 121 lines

How it starts

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

Ship the roadmap (autopilot)

Found once, then run the driver-fired loop (Claude /loop, external driver, or manual re-invocation): plan, implement, review, open and optionally merge one PR per roadmap unit. After the roadmap, sweep existing issues, ship fix-now work, report residue as proposals (never create backlog automatically), and print the final report. Use strong tiers for judgment, cheap tiers for typing, and humans at expensive-to-undo decisions.

ship-roadmap is the conductor of the loop. It emits its native fixed SHIP: banner and closing → Next: block; the package-owned machine-result profiles apply to the worker and sensor skills that a driver invokes inside the loop.

Turn contract — verify before ending the turn

✓ Exactly ONE stage advanced (or a terminal banner printed) and ONE line appended to the run log
✓ Nothing was merged outside the active --fullauto wrapper; direct merge
  commands remained blocked and no authorization survived the iteration
✓ Artifact language: explicit user instruction > the project's declared docs language > English. The CONVERSATION language never decides — a Spanish prompt still produces English PRs/issues/commits/SPECs unless one of the first two says otherwise
✓ The closing `→ Next:` block is printed as the ABSOLUTE last output

Any unchecked box means the turn is not done.

When to use

Use for a locked roadmap with supervision at merge/end points. For one feature, one bug, or exploratory work use the manual planning/execution flow instead.

Step 0 — Discover the project (always first)

Read before acting: CLAUDE.md/AGENTS.md Workflow conventions, documentation map, docs/features/ROADMAP.md, fix index, architecture doc, and .github/ templates. Then establish:

  1. Substrate: if the guide, map, roadmap and fix index exist, skip founding and confirm their answers; otherwise founding creates missing pieces.
  2. Skills: verify plan-feature, execute-phase, review-change, and audit-pr are installed and record their directory for worker prompts. If absent, stop with npx skills add gtrabanco/agentic-workflow. With --fullauto, also require executable .agentic-workflow/hooks/fullauto-merge.sh and its platform guard; otherwise route to init-workspace, never direct merge.
  3. Run: existing docs/features/SHIP_DECISIONS.md or an open docs/ship-founding PR means resume with --continue; bare invocation reports status instead of founding again.
  4. Shape: greenfield/existing, branch, and dirty tree; unexplained dirty default branch stops (never clean it silently).

Read the full file on GitHub · 121 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.

  1. today Changed a72799a78d79
  2. 4d ago First seen · 121 lines · 59 tokens per session scan A 23c50119bf2a

Subscribe to this mod's changes

ship-roadmap is a skill published in the GitHub repository gtrabanco/agentic-workflow (20 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,735 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

offensive-mitigations

Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.

SnailSploit/Claude-Red · 0 tokens

offensive-exploit-development

Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.

SnailSploit/Claude-Red · 0 tokens

offensive-advanced-redteam

Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC…

SnailSploit/Claude-Red · 146 tokens

offensive-dependency-confusion

Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI…

SnailSploit/Claude-Red · 234 tokens

offensive-phishing

Phishing campaign execution methodology for authorized red team engagements. Covers end-to-end campaign lifecycle: infrastructure provisioning (GoPhish, SMTP relay configuration, domain acquisition and aging, SPF/DKIM/DMARC alignment), payload delivery vectors (Office macro weaponization, HTA droppers, ISO/IMG…

SnailSploit/Claude-Red · 276 tokens

offensive-active-directory

Active Directory attack methodology for internal network red team engagements. Covers reconnaissance (BloodHound, PowerView, ADExplorer), credential abuse (Kerberoasting, ASREProasting, NTLM relay, LLMNR/NBT-NS poisoning), privilege escalation (ACL abuse, GPO abuse, unconstrained/constrained delegation), lateral…

SnailSploit/Claude-Red · 167 tokens