closeout-pack
Skill1 starsChanged 23 days agoMITView on GitHub
Produces a closeout pack when an engagement or programme needs formal acceptance, performance assessment and residual action ownership.
In this repository133 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- access-control-auditSkill
- ai-opportunity-scanSkill
- ai-policy-writerSkill
- annual-budget-builderSkill
- application-portfolio-mapSkill
- architecture-fit-checkSkill
- automation-backlogSkill
- benefits-realisationSkill
- board-paperSkill
- bottleneck-removalSkill
- break-even-modelSkill
- budget-variance-analystSkill
- business-continuity-plannerSkill
- business-valuationSkill
- capacity-planningSkill
- case-study-writerSkill
- cash-flow-forecastSkill
- change-adoptionSkill
- change-impactSkill
- channel-profitabilitySkill
- churn-cohort-analysisSkill
- client-handoverSkill
- client-kickoffSkill
- client-profitabilitySkill
- client-relationship-managerSkill
- compensation-bandsSkill
- competitor-mapperSkill
- contribution-marginSkill
- cost-structure-analystSkill
- crisis-communicationsSkill
- customer-insight-synthesiserSkill
- customer-interview-designerSkill
- customer-journey-mapSkill
- customer-segmenterSkill
- cyber-risk-assessmentSkill
- dashboard-requirements-plannerSkill
- data-lineage-mapperSkill
- data-quality-auditSkill
- decision-logSkill
- decision-memoSkill
- decision-rightsSkill
- delivery-model-selectorSkill
- demand-validatorSkill
- discount-governanceSkill
- discovery-call-facilitationSkill
- discovery-call-prepSkill
- discovery-question-designSkill
- discovery-synthesisSkill
- engagement-outcomesSkill
- evidence-synthesiserSkill
- executive-dashboardSkill
- executive-summarySkill
- fee-settingSkill
- financial-statement-diagnosticSkill
- fundraising-readinessSkill
- funnel-diagnosticSkill
- go-to-marketSkill
- governance-designerSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 9
Use at formal closure after outputs are delivered and operational ownership has transferred.
- Distinctive: line 21
Run a structured retrospective across strengths, gaps and root causes.
- Distinctive: line 26
Use: Closure Summary, Objectives and Outcomes, Delivery Performance, Benefits Position, Lessons, Residual Risks, Open Actions, Archive …
- Distinctive: line 30
Every residual item has an owner and due date.
≈ “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
Closeout Pack
When to use it
Use at formal closure after outputs are delivered and operational ownership has transferred.
What Claude needs
- client-context.md and approved scope
- Baseline objectives, milestones and acceptance criteria
- Final outcomes, expenditure position and benefit evidence
- Open actions, residual risks and stakeholder input
Method
- Compare delivered outcomes with scope, baseline and acceptance criteria.
- Reconcile milestones, resources, changes and outstanding obligations.
- Assess expected benefits and schedule remaining measurement points.
- Run a structured retrospective across strengths, gaps and root causes.
- Transfer residual risks and actions to named operational owners.
- Record acceptance, archive requirements and closure approvals.
Output format
Use: Closure Summary, Objectives and Outcomes, Delivery Performance, Benefits Position, Lessons, Residual Risks, Open Actions, Archive Index and Sign-off.
Quality checks
- Outcome claims are supported by acceptance evidence.
- Every residual item has an owner and due date.
- Closure status matches contractual and governance requirements.
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.