make-deliverable
Skill1 starsChanged 3 months agoMITView on GitHub
Produce a stakeholder-ready deliverable — executive summary, status update, steering-committee/board deck, or announcement — tailored to a specific audience. Use to package PMO substance for communication. Dispatches the comms-lead. Supports optional tool sync.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- link7373/agentic-bi-teamtheir own version, first seen Sep 23, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- link7373/agentic-bi-team★ 4same name
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 repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-business-caseSkill
- build-roadmapSkill
- capture-feedbackSkill
- close-projectSkill
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- groom-backlogSkill
- manage-changeSkill
- manage-resourcesSkill
- plan-capacitySkill
- plan-launchSkill
- plan-portfolio-automationSkill
- plan-projectSkill
- plan-sprintSkill
- powerbiSkill
- prioritizeSkill
- review-okrsSkill
- review-portfolio-intakeSkill
- run-ceremonySkill
- run-discoverySkill
- run-gate-reviewSkill
- setup-pmoSkill
- track-financialsSkill
- track-portfolioSkill
- track-statusSkill
- write-prdSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Use RAG with reason + action.
- Very specific: line 25
Put detail in appendices or link to the canonical knowledge/ artifact.
- Very specific: line 26
Check every number traces to a knowledge/ file.
- Very specific: line 33
Start from the matching template — templates/exec-update.md, templates/status-report.md, or templates/steerco-pack.md for a steering …
- Very specific: line 41
If knowledge/integrations.md configures Slack/Notion, offer to post/share the deliverable there.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
/make-deliverable — Package it for the audience
When to use
Turning PMO substance (status, roadmap, plan, decision) into a polished, audience-specific communication.
Dispatches
comms-lead (lead). Pull substance from the relevant agent first (delivery-monitor for status,
product-manager for roadmap, etc.) — never fabricate content.
Inputs
The source substance/artifact, knowledge/stakeholder-map.md, knowledge/product-context.md. For a steering
committee: knowledge/portfolio/, knowledge/status/, knowledge/financials.md, knowledge/raid-log.md,
knowledge/change-log.md, and recent gate records in knowledge/programs/.
Steps
- Identify the audience and the decision/action they need.
- Lead with the bottom line (BLUF); match altitude (executives → outcomes/decisions; teams → detail).
- Use RAG with reason + action; quantify where possible; flag uncertainty honestly.
- Format to the requested medium (one-pager, deck outline, email, announcement); keep it scannable.
- Put detail in appendices or link to the canonical
knowledge/artifact. - Check every number traces to a
knowledge/file. A deliverable is a rendering, not a source — if you need a fact that doesn't exist upstream, send it back to the agent that owns it rather than deriving it here.
Methods
standards/communication-standards.md (primary), knowledge/methods/roadmapping.md (audience views).
Output
Start from the matching template — templates/exec-update.md, templates/status-report.md, or
templates/steerco-pack.md for a steering committee. Save to knowledge/deliverables/ as
YYYY-MM-DD-<audience>-<topic>.md; log only consequential communication decisions to
knowledge/decision-log.md. Circulated deliverables are never edited — supersede them with a new dated file so
the record of what was said, and when, stays intact. Follow standards/communication-standards.md and
standards/document-standards.md.
Optional sync
If knowledge/integrations.md configures Slack/Notion, offer to post/share the deliverable there. Skip if
not configured.
Created by Colin Beck<br>
LinkedIn: https://www.linkedin.com/in/beckcolin/<br>
GitHub: https://github.com/link7373
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.