dispatching-gap-analysis

A skill that sends a separate review agent to compare delivered code with specifications, tests, and verification evidence, then return a structured list of gaps.

In plain words
What is it for?
Use it during feature or sprint review to identify missing requirements and run the defined self-check process.
Why use it?
It gives review work a fresh context and keeps follow-up actions, task updates, and user-facing results under the main workflow.

Skill for Claude CodeCodex

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/acendas/shipyard/dispatching-gap-analysis
Any agent
npx skills add Acendas/shipyard --skill dispatching-gap-analysis
Clone the repo
git clone --depth 1 https://github.com/Acendas/shipyard

Made for: Claude Code, Codex.

Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,091 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.00013 $0.01091
Opus 5 $0.00006 $0.00545
Sonnet 5 $0.00003 $0.00218
Haiku 4.5 $0.00001 $0.00109

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

Security

Grade A, and why

dispatching-gap-analysis 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.

plugins/shipyard/skills/dispatching-gap-analysis/SKILL.md · 103 lines

How it starts

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

Dispatching Gap Analysis

Runs /ship-review Stage 4 + Stage 4.5 as a fresh-context registered agent. The agent reads specs, delivered-code evidence, test captures, spec-review findings, and goal-verification results, then returns a structured gap list and the 10-check self-review result. The orchestrator owns all side effects: classification actions, cursor advances, stuck-counter computation, task/IDEA creation, user-facing surfacing, and read-only enforcement.

Inputs

  • scope"feature" | "sprint"
  • target_ids — feature IDs, or null when scope is sprint.
  • base_ref / head_ref — diff range.
  • data_dir — literal <SHIPYARD_DATA> path.
  • sprint_spec_paths — feature/task/reference paths under <SHIPYARD_DATA>/spec/.
  • evidence_paths — Stage 1 test captures, Stage 1b spec-review findings, and Stage 3 goal-verification artifacts gathered so far.

Dispatching the Analyst

The gap-analysis methodology, classification boundaries, read-only contract, and Required Return Shape live in the registered agent agents/shipyard-gap-analyst.md — read it once if you need to know exactly what it does; do not re-inline it here.

Model tier (think). Read models.think from config.md — the invoking command skill's ! context block, or a Read of <SHIPYARD_DATA>/config.md. If the value is non-empty, pass model: <value> in the Agent call; if empty or absent, OMIT the model: field entirely so the subagent inherits the session model. Never hardcode a model literal.

Effort tier (think). Read agent_effort.think from config.md; default high. If the value is non-empty, pass effort: <value> in the Agent call; if empty or absent, OMIT effort: so the subagent inherits the runtime default.

Dispatch:

Agent(
  subagent_type: "shipyard:shipyard-gap-analyst",
  model: <models.think value, or omit>,
  effort: <agent_effort.think value, or omit>,
  prompt: "
    Scope:              {{scope}}
    Target IDs:          {{target_ids}}
    Base ref:            {{base_ref}}
    Head ref:            {{head_ref}}
    Data dir:            {{data_dir}}
    Sprint/spec paths:   {{sprint_spec_paths}}
    Evidence paths:      {{evidence_paths}}
  "
)

Read the full file on GitHub · 103 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. 2d ago First seen · 103 lines · 13 tokens per session scan A fb6401ca0f19

Subscribe to this mod's changes

dispatching-gap-analysis is a skill published in the GitHub repository Acendas/shipyard (2 stars, last pushed 20d ago), licensed MIT. It adds 13 tokens to every session and 1,091 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

engenharia-de-requisitos

Use when doing requirements engineering, business analysis, or the software-engineering stage of discovering / specifying / validating / managing requirements — the stage BEFORE code (what to build) and AFTER (was the right thing built?), for new projects and for evolutions of existing ones. Triggers (EN)…

seekdevcore/sk-requirements-engineering-theskill · 0 tokens

engenharia-de-requisitos

Use when doing requirements engineering, business analysis, or the software-engineering stage of discovering / specifying / validating / managing requirements — the stage BEFORE code (what to build) and AFTER (was the right thing built?), for new projects and for evolutions of existing ones. Triggers (EN)…

seekdevcore/sk-requirements-engineering-theskill · 0 tokens

write-epic

Produces a complete epic definition following Atlassian agile guidance. An epic captures a large initiative that is too big for a single sprint and must be decomposed into user stories.

MarieLynneBlock/arcanum-artifex · 40 tokens

write-user-story

Produces a complete, ready-to-groom user story following the standard Atlassian/agile format. It applies the INVEST criteria and the 3 Cs framework (Card, Conversation, Confirmation) to ensure each story is well-scoped, valuable, and testable — not just syntactically correct.

MarieLynneBlock/arcanum-artifex · 64 tokens

rulesync

Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.

dyoshikawa/rulesync · 64 tokens

agent-workspace-linux

Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…

ilysenko/codex-desktop-linux · 70 tokens