agentleFS
stevemarksavastevemarksava/superteam/.claude/skills/deliver/SKILL.md

deliver

Skill1 starsChanged 2 months agoMITView on GitHub

Full Superteam delivery chain — Vera sign-off, README, commit, push, confirm hook

  • Commits and pushes

28 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • matthewpSkill

    prune

    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

  • sahinSkill

    create-issue

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 5 projects that use this

  • SentrySkill

    spec

    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

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 5 projects that use this

  • AWSSkill

    wait-what

    Stop. That last message did not land: re-pitch it.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 3

    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
  1. Distinctive:

    Do any agent files reference concepts, agents, or tools that no longer exist?

    line 24
  2. Distinctive:

    Do onboarding docs, CLAUDE.md, or AGENTS.md need updating to reflect what changed?

    line 25
  3. Distinctive:

    If Kevin confirms everything is current, note: "Kevin: docs current." and continue.

    line 30
  4. Distinctive:

    Delete all squad sentinel files before staging.

    line 38
  5. Distinctive:

    Run git status to see what's changed.

    line 51
  6. Distinctive:

    Write a commit message that captures WHAT changed and WHY.

    line 57
  7. Distinctive:

    Do NOT amend. Create a new commit.

    line 68
  8. Very specific:

    If the branch has no upstream, use git push -u origin <branch>.

    line 77
  9. Distinctive:

    After push, confirm the PostToolUse/Coach hook ran by checking if a game tape file was written today:

    line 81
  10. Very specific:

    Check .squad/coach/game-tape/YYYY-MM-DD.md (today's date)

    line 82
  11. Distinctive:

    If it exists and has content, report: "Coach game tape written."

    line 83
  12. Very specific:

    If it doesn't exist, note: "Coach hook did not fire — check settings.json hooks config."

    line 84

“Common” is measured: kept by at least 6 in 10 of the 28 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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 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 3 — Update README(s)

Apply Kevin's documentation findings. Update all flagged files. If Kevin flagged nothing, skip this step and note it.

Step 3 — 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
  • active-task.md — resets the pre-edit hook so the next /decide starts clean
  • vera-approved.md — consumed by the push gate; cleared so the next delivery requires a fresh Vera sign-off
  • kryptonite-cleared.md — consumed by the build gate; cleared so the next build requires a fresh Kryptonite review

Step 4 — 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 5 — 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 6 — Push

Push to origin:

git push

If the branch has no upstream, use git push -u origin <branch>.

Step 7 — 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."

Step 8 — 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 fire

That's it. Clean, complete, no loose ends.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.