agentmods.dev

delivery-flow

delivery-flow is a skill for Claude Code from P47Phoenix/Claude-Plugins. It costs 168 tokens per session (6,741 once invoked), scanned A, original, MIT.

A delivery pipeline coordinator that guides a project through seven stages, from the initial idea through refinement, design, architecture, planning, development, and user acceptance testing. User acceptance testing checks the finished work from the user's point of view.

In plain words
What is it for?
Use it to coordinate requirements, design, architecture, implementation, testing, and final acceptance across a software or hardware project.
Why use it?
It gives teams a structured path for moving work forward and includes reviews, correction loops, and checks that the result meets the team's completion rules.

Skill for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: model in frontmatter; reads .claude/ paths; mentions subagents.

Part of the delivery-team plugin — 17 skills shipped together

not rated 2repo 2d ago A scan 168 tokens original MIT

Good fit Use it to coordinate requirements, design, architecture, implementation, testing, and final acceptance across a software or hardware project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/p47phoenix/claude-plugins/delivery-flow
View source ↗ P47Phoenix/Claude-Plugins
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.

Any agent
npx skills add P47Phoenix/Claude-Plugins --skill delivery-flow
Clone the repo
git clone --depth 1 https://github.com/P47Phoenix/Claude-Plugins

Made for: Claude Code.

Or install delivery-team, the plugin that ships this one along with the rest of its 17 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 delivery-flow

README.md
[![agentmods](https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/delivery-flow/github.svg)](https://agentmods.dev/skills/p47phoenix/claude-plugins/delivery-flow)
Your own site
<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/delivery-flow"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/delivery-flow/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.

agentmods 80×15 button for delivery-flow

Your own site · 80×15
<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/delivery-flow"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/delivery-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 168 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,741 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00168 $0.06741
Opus 5.5 $0.00067 $0.02696
Sonnet 5.5 $0.00034 $0.01348
Haiku 4.5 $0.00017 $0.00674

Measured 1mo ago against content hash 43067c9e07e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

delivery-flow 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 1mo 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.

delivery-team/skills/delivery-flow/SKILL.md · 500 lines

How it starts

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

Delivery Flow Orchestrator

Design Principle

This skill is the ORCHESTRATOR. It coordinates the delivery team through a structured pipeline but NEVER produces domain artifacts directly. All domain work — requirements, designs, architecture, code, tests, plans — is delegated to worker skills operating as sub-agents with isolated context. Full doctrine elaboration, Core Principles 1–7, Anti-Patterns catalogue, and Guardrails detail: see delivery-team/references/shared/orchestrator-doctrine.md.

Model awareness (Opus 4.7 / F-08): Under F-08, the 4.7 runtime dispatches fewer sub-agents by default unless explicitly steered. "One Role = One Sub-Agent" (Phase 4) is a behaviourally load-bearing gate, not a style preference. Role-count under-dispatch is the highest-confidence regression mode on 4.7.

Phase 0: Setup Wizard

Before the pipeline executes, check for project configuration:

State Detection (Resume Check)

Before checking config, check for an existing pipeline state:

  1. Check for .delivery/state.md in the current working directory.
  2. If state exists with status: in_progress:
    • Read the YAML frontmatter to load pipeline state.
    • Announce: > Existing pipeline found: [pipeline_id], started [date], last completed Stage [N] ([name]). Currently at Stage [N+1].
    • Validate: verify all artifact files in the artifacts map exist on disk. If any are missing, announce which and offer: Restart from that stage / Abandon.
    • Semantic validation: current_stage in range 1-7, not in stages_completed, no gaps in completed+skipped.
    • Config divergence check: diff config_snapshot against current .delivery/config.yml. If different, warn: "Config has changed since this pipeline started. Resume uses the original config. Choose Restart to apply new config."
    • Offer the user: Resume / Restart / Abandon
    • Resume: load config from snapshot, skip completed stages, start at current_stage.
    • Restart: move state file to .delivery/state-archive/state-<timestamp>.md (cap at 5, delete oldest), start fresh.
    • Abandon: delete state file, no pipeline runs.
  3. If state exists with status: aborted:
    • Announce: > Aborted pipeline found from [date], stopped at Stage [N]. Artifacts from stages [list] are preserved.
    • Offer: Resume / Restart / Abandon (same as above).
  4. If state exists with status: completed: ignore (previous run finished normally).
  5. If no state file exists: proceed to config check (normal flow).

Read the full file on GitHub · 500 lines

Files

What ships with it

60 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.

  1. 1mo ago First seen · 500 lines · 168 tokens per session scan A 43067c9e07e0

Subscribe to this mod's changes

delivery-flow is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 168 tokens to every session and 6,741 once invoked, about $0.0007 per session on Opus 5.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.

PlanningProject management
Related

Other skills, from other repositories

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

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

recipe-create-meet-space

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

googleworkspace/cli · 18 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

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

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens