close-project
Skill1 starsChanged 3 months agoMITView on GitHub
Close a project properly — accept or descope every deliverable, record final cost and schedule variance, hand benefits to named owners, resolve or transfer open RAID entries, release resources, and capture lessons. Use at completion or cancellation. Dispatches the project-manager.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tinamkemp/claude-skillstheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tinamkemp/claude-skills★ 0same 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
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- groom-backlogSkill
- make-deliverableSkill
- 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
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 9
When a project completes, is cancelled, or is superseded.
- Very specific: line 28
Hand over the benefits: Every benefit from the business case goes to a named owner *outside the project team*, with a first review date, …
- Distinctive: line 31
Clear the RAID log: Every open entry is resolved, transferred to a named owner, or explicitly accepted.
- Very specific: line 33
Release the resources: Update allocations in knowledge/resources.md, and close out vendor and contract obligations — including any …
- Very specific: line 48
Start from templates/closure-report.md.
- Very specific: line 55
If knowledge/integrations.md configures Jira/Linear/Notion, offer to close or archive the project's board and post the closure summary.
≈ “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
/close-project — Finish, don't fade
When to use
When a project completes, is cancelled, or is superseded. Cancellations need this most — they carry the most valuable lessons and are the most likely to be skipped because nobody wants to write the report.
Dispatches
project-manager (lead) + financial-analyst (final actuals and benefits handoff) + governance-lead
(closure quality gate and lessons curation) + scrum-master (harvest retro actions and team lessons) +
resource-manager (release allocations).
Inputs
The project plan in knowledge/projects/, knowledge/status/ history, knowledge/raid-log.md,
knowledge/change-log.md, knowledge/financials.md, knowledge/ceremonies/ (retro notes),
knowledge/resources.md, knowledge/portfolio.md.
Steps
- Compare delivered against baselined scope, accounting for approved changes in
knowledge/change-log.md. Anything not delivered is formally descoped with a destination — backlog, another project, or dropped — not left ambiguous. - Record final schedule and cost variance. Baseline vs. actual with the reason. Where no cost baseline existed, say so — do not reconstruct one at closure to produce a tidy variance.
- Hand over the benefits. Every benefit from the business case goes to a named owner outside the project
team, with a first review date, recorded in the benefits register in
knowledge/financials.md. The team disbands; benefits take quarters. This is the step whose absence makes claimed value disappear. - Clear the RAID log. Every open entry is resolved, transferred to a named owner, or explicitly accepted. Nothing is closed by being ignored.
- Release the resources. Update allocations in
knowledge/resources.md, and close out vendor and contract obligations — including any knowledge transfer that was supposed to happen before a contract ended. - Capture lessons that would change behavior. "Communication could be better" is a feeling; a specific
recommendation someone could act on is a lesson. Append each to
knowledge/lessons-learned.md, and check whether it is the third occurrence of a pattern — if so, change the standard, template, or skill rather than filing another row. - Close the record. Set the register row in
knowledge/portfolio.mdto Closed and log the closure decision, including the reason for a cancellation.
Methods
knowledge/methods/governance-and-change.md (closure, lessons that get read, cancellations),
knowledge/methods/financial-management.md (benefits handoff),
knowledge/methods/project-management.md (closing a project).
Output
Start from templates/closure-report.md. Save to knowledge/projects/<name>-closure.md; update
knowledge/financials.md (final actuals, benefits owners), knowledge/resources.md (released allocations),
knowledge/raid-log.md (closed/transferred), knowledge/lessons-learned.md (appended), and
knowledge/portfolio.md (status Closed). Log the closure in knowledge/decision-log.md. Follow
standards/document-standards.md.
Optional sync
If knowledge/integrations.md configures Jira/Linear/Notion, offer to close or archive the project's board
and post the closure summary. Files remain source of truth; 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.