deliver
Skill1 starsChanged 2 months agoMITView on GitHub
Full Superteam delivery chain — Vera sign-off, README, commit, push, confirm hook
- Commits and pushes
25 other projects use a version of this.
Adopted by
Most recently taken up by
- zahidakhyar/skillstheir own version, first seen Nov 8, 2026
- frostney/knipstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- mblauberg/provenanttheir own version, first seen Nov 8, 2026
- AcKeskin/contexturetheir own version, first seen Nov 1, 2026
Used with
Projects with it also use prune, create-issue and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
matthewpSkillprune
Find and remove unused CSS in a Tideway project — classes defined in stylesheets but never referenced in markup. Use whenever the user wants to prune dead CSS, find unused styles or classes, clean up or slim a stylesheet, find orphaned BEM classes, or "tree-shake" hand-written CSS.
Also in 3 projects that use this
sahinSkillcreate-issue
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 5 projects that use this
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 4 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 5 projects that use this
AWSSkillwait-what
Stop. That last message did not land: re-pitch it.
Also in 3 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- google-gemini/gemini-managed-agents-templates★ 99same name
- domengabrovsek/agent-config★ 22same name
- domengabrovsek/claude★ 22same name
- domitriusclark/claude-skills★ 11same name
- coder-xieshijie/dev-skills★ 5same name
- AcKeskin/contexture★ 2same name
- andeeplus/aplus★ 2same name
- MarkTripoli/skills★ 2same name
- matiopala/skills★ 2same name
- dcguim/skills★ 1same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- decideSkill
- deliverSkill
- researchSkill
- sprintSkill
- superteam-coachSkill
- superteam-coachSkill
- azure-ai-foundry-devSkill
- azure-devopsSkill
- bc-mcpSkill
- copilot-studio-buildSkill
- decideSkill
- erp-connectorsSkill
- fabric-appsSkill
- fabric-medallionSkill
- fabric-notebooksSkill
- fabric-onelakeSkill
- fabric-power-biSkill
- find-skillsSkill
- mirrorSkill
- ontologySkill
- playwrightSkill
- researchSkill
- sap-btp-agentsSkill
- semantic-reasoningSkill
- semantic-searchSkill
- sprintSkill
- superteam-coachSkill
- superteam-demoSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 11 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 13
Before doing anything else, write .squad/deliver-started.md with this exact content:
- Very specific: line 19
Use today's date and current time.
- Distinctive: line 36
Do any agent files reference concepts, agents, or tools that no longer exist?
- Distinctive: line 37
Do onboarding docs, CLAUDE.md, or AGENTS.md need updating to reflect what changed?
- Distinctive: line 42
If Kevin confirms everything is current, note: "Kevin: docs current." and continue.
- Distinctive: line 50
If no ADRs exist for this delivery, note: "No ADRs to update." and continue.
- Distinctive: line 58
Delete all squad sentinel files before staging.
- Very specific: line 77
Do NOT delete deliver-started.md here — it must survive until after push so the Coach hook can read it.
- Distinctive: line 81
Run git status to see what's changed.
- Distinctive: line 87
Write a commit message that captures WHAT changed and WHY.
- Distinctive: line 98
Do NOT amend. Create a new commit.
- Very specific: line 107
If the branch has no upstream, use git push -u origin <branch>.
- Distinctive: line 111
After push, confirm the PostToolUse/Coach hook ran by checking if a game tape file was written today:
- Very specific: line 112
Check .squad/coach/game-tape/YYYY-MM-DD.md (today's date)
- Distinctive: line 113
If it exists and has content, report: "Coach game tape written."
- Very specific: line 114
If it doesn't exist, note: "Coach hook did not fire — check settings.json hooks config."
- Distinctive: line 116
After confirming the game tape, delete the delivery sentinel:
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/deliver — Superteam Delivery Checklist
You are executing the Superteam delivery chain. Follow every step in order. Do not skip steps. Do not ask the user whether to proceed between steps — just do them.
Step 0 — Write Delivery Sentinel
Before doing anything else, write .squad/deliver-started.md with this exact content:
DELIVER STARTED — YYYY-MM-DD HH:mmUse today's date and current time. This sentinel tells post-push-coach.ps1 that /deliver was invoked. Without it, Coach marks the session as an unscored /decide miss.
Step 1 — Vera Sign-Off (Mandatory)
Brief Vera on everything that was just built or changed. Give her:
- What was built (files changed, features added)
- What it's supposed to do
- Any edge cases you already considered
Vera must explicitly approve before proceeding. If she flags issues, fix them first, then restart the deliver chain from Step 1.
Step 2 — Kevin Documentation Audit
Brief Kevin on what changed. He checks:
- Does the README need updating? (new features, changed commands, new files, removed things)
- Do any agent files reference concepts, agents, or tools that no longer exist?
- Do onboarding docs, CLAUDE.md, or AGENTS.md need updating to reflect what changed?
- Are there any squad docs (SYSTEM.md, PLAYBOOK.md, CEREMONIES.md) that are now stale?
Kevin flags specific files that need updating. Fix all flagged files before proceeding.
If Kevin confirms everything is current, note: "Kevin: docs current." and continue.
Step 2b — Update ADR Status
Find all files in .squad/decisions/ with status: decided or status: proposed that were part of this delivery. Update the status field to status: implemented.
To identify which ADRs apply: check decision files modified in this session or referenced in the active task. If unsure, scan .squad/decisions/ for files dated today or containing the feature/task name.
If no ADRs exist for this delivery, note: "No ADRs to update." and continue.
Step 3 — Update README(s)
Apply Kevin's documentation findings. Update all flagged files. If Kevin flagged nothing, skip this step and note it.
Step 4 — Clear All Sentinels
Delete all squad sentinel files before staging. These are all gitignored:
Remove-Item .squad/active-task.md -ErrorAction SilentlyContinue
Remove-Item .squad/vera-approved.md -ErrorAction SilentlyContinue
Remove-Item .squad/kryptonite-cleared.md -ErrorAction SilentlyContinue
Remove-Item .squad/pod-routed.md -ErrorAction SilentlyContinue
Remove-Item .squad/kevin-docs-checked.md -ErrorAction SilentlyContinue
Remove-Item .squad/marlo-specced.md -ErrorAction SilentlyContinue
Remove-Item .squad/playwright-results.md -ErrorAction SilentlyContinueactive-task.md— resets the pre-edit hook so the next /decide starts cleanvera-approved.md— consumed by the push gate; cleared so the next delivery requires a fresh Vera sign-offkryptonite-cleared.md— consumed by the build gate; cleared so the next build requires a fresh Kryptonite reviewpod-routed.md— consumed by the build gate; cleared so the next build requires a fresh Eric pod routing recordkevin-docs-checked.md— consumed by the commit gate; cleared so the next commit requires a fresh Kevin doc reviewmarlo-specced.md— consumed by the UI build gate; cleared so the next UI feature requires a fresh committed Marlo specplaywright-results.md— consumed by the push gate; cleared so the next web delivery requires a fresh Playwright run
Do NOT delete deliver-started.md here — it must survive until after push so the Coach hook can read it.
Step 5 — Stage Changes
Run git status to see what's changed. Stage only the relevant files for this delivery — not unrelated uncommitted changes. Do NOT use git add -A unless every changed file belongs to this delivery.
Show the staged list before committing.
Step 6 — Commit
Write a commit message that captures WHAT changed and WHY. Format:
<type>: <what changed>
<why it was needed — one sentence if non-obvious>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>Types: feat, fix, refactor, docs, chore, test
Do NOT amend. Create a new commit.
Step 7 — Push
Push to origin:
git pushIf the branch has no upstream, use git push -u origin <branch>.
Step 8 — Confirm Coach Hook
After push, confirm the PostToolUse/Coach hook ran by checking if a game tape file was written today:
- Check
.squad/coach/game-tape/YYYY-MM-DD.md(today's date) - If it exists and has content, report: "Coach game tape written."
- If it doesn't exist, note: "Coach hook did not fire — check settings.json hooks config."
After confirming the game tape, delete the delivery sentinel:
Remove-Item .squad/deliver-started.md -ErrorAction SilentlyContinueThis must be the last sentinel deleted — the post-push Coach hook reads it during the push; deleting it earlier defeats the M3 compliance check.
Step 9 — Report to Steve
End with a clean delivery summary:
DELIVERED — <what was shipped>
Vera: approved
Commit: <short hash> — <message>
Push: origin/<branch>
Coach: game tape written / hook did not fireThat's it. Clean, complete, no loose ends.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

