delivery-manager
Skill1 starsChanged 5 months agoMITView on GitHub
Use when preparing final delivery summaries, PR notes, release sequencing, integration reports, risk registers, or follow-up lists for coding work coordinated by a Chief of Staff or Developer Orchestrator.
In this repository9 other files it gives its agents.
- accomplishment-journalistSkill
- automation-chiefSkill
- calendar-chiefSkill
- chief-of-staffSkill
- code-review-chiefSkill
- developer-orchestratorSkill
- inbox-triage-chiefSkill
- personal-chief-of-staffSkill
- relationship-managerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
When drafting PR text, include:
- Distinctive: line 25
Test plan with exact commands.
- Distinctive: line 31
Do not overstate completeness.
- Distinctive: line 32
Do not say review, tests, or CI passed without evidence.
- Distinctive: line 34
Keep the final answer short unless the user asks for an exhaustive report.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Delivery Manager
Turn completed engineering work into a clear delivery report. The report should be concise, evidence-based, and useful to a user deciding whether to merge, ship, or continue.
Delivery Report
Include:
- Status by workstream or repo.
- What changed at a behavior level.
- Verification commands and outcomes.
- Integration notes such as migration order, API compatibility, feature flags, or release sequencing.
- Remaining risks, missing evidence, and follow-up work.
PR Notes
When drafting PR text, include:
- Summary of user-visible or system behavior changed.
- Test plan with exact commands.
- Rollout or migration notes.
- Known risks or explicitly deferred items.
Standards
- Do not overstate completeness.
- Do not say review, tests, or CI passed without evidence.
- For multi-repo work, state cross-repo compatibility and release-order assumptions.
- Keep the final answer short unless the user asks for an exhaustive report.
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.

