debrief
Skill3 starsChanged 3 months agoMITView on GitHub
Turn meeting or work-session notes into filed history, decisions, tasks, waiting-for items, and follow-up drafts. Use after any session worth capturing. Triggers on "debrief", "debrief this", "process these notes", and "file this meeting".
30 other projects use a version of this.
Adopted by
Most recently taken up by
- srizzon/skillstheir own version, first seen Nov 8, 2026
- kiloloop/oacp-skillstheir own version, first seen Nov 1, 2026
- piotrmechlinski/executive-braintheir own version, first seen Nov 1, 2026
- pedroromeroluna/peter-braintheir own version, first seen Nov 1, 2026
- bks-lab/open-bridgetheir own version, first seen Oct 30, 2026
- adamlinscott/claude-skillstheir own version, first seen Oct 30, 2026
Used with
Projects with it also use brief, review and 1 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.
AnthropicSkillbrief
Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- suboss87/FDEOps★ 940same name
- spacedock-dev/spacedock★ 85same name
- bks-lab/open-bridge★ 13same name
- pedroromeroluna/peter-brain★ 9same name
- trydebrief/debrief-skills★ 4same name
- uttambharadwaj/kb-graph★ 4same name
- adamlinscott/claude-skills★ 3same name
- armenr/modelmux★ 2same name
- siemendev/release-process★ 2same name
- aaronwskinner/claude-skills★ 1same name
20 more not listed
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 repository6 other files it gives its agents.
- company/AGENTS.mdAGENTS.md
- company/CLAUDE.mdCLAUDE.md
- meeting-notesSkill
- morning-sweepSkill
- reflectSkill
- weekly-updateSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
10
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
- Distinctive: line 10
Done when: every decision, task, and waiting item from the session has a filed home, and a dated entry exists in history.
- Very specific: line 16
Company mode: use this when operating-system/ exists with operating-system/GLOBAL_TASKS.md.
- Very specific: line 17
Personal mode: use this when root-level TASKS.md and debrief-history.log exist.
- Distinctive: line 18
Both detected: ask which mode to use. Write nothing until the user chooses.
- Distinctive: line 21
Do not create a structure just to make the skill run.
- Distinctive: line 25
Read the source notes fully.
- Distinctive: line 34
Do not invent a decision or task.
- Very specific: line 41
Add new open tasks to root TASKS.md.
- Distinctive: line 42
Update an existing root or area CLAUDE.md only when current state or a durable fact changed.
- Distinctive: line 48
Use the top-level operating system, not project folders:
- Distinctive: line 57
Do not create another meeting-note file when the supplied source is already a note file.
- Distinctive: line 63
every file you plan to touch
- Distinctive: line 68
Wait for approval. Write only the approved changes.
“Common” is measured: kept by at least 6 in 10 of the 27 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.
Files
Debrief
Turn rough notes into filed action without losing the story.
Done when: every decision, task, and waiting item from the session has a filed home, and a dated entry exists in history.
Detect the structure first
Inspect the current folder before planning any write.
- Company mode: use this when
operating-system/exists withoperating-system/GLOBAL_TASKS.md. - Personal mode: use this when root-level
TASKS.mdanddebrief-history.logexist. - Both detected: ask which mode to use. Write nothing until the user chooses.
- Neither detected: say that this folder does not contain a recognised personal or company structure. Point the user to START-HERE. Write nothing.
Do not create a structure just to make the skill run.
Extract the signal
Read the source notes fully. Pull out:
- a two or three line summary
- decisions and their reasoning
- the user's open tasks
- things waiting on other people
- follow-up drafts
- durable facts or changed current state
Do not invent a decision or task. If something was discussed but not decided, label it as discussed. Flag legal, financial, HR, and other sensitive material before proposing a write.
Route in personal mode
Personal mode has three homes:
- Append the dated session narrative, including decisions and reasoning, to
debrief-history.log. - Add new open tasks to root
TASKS.md. Remove or check completed tasks instead of keeping stale open items. - Update an existing root or area
CLAUDE.mdonly when current state or a durable fact changed. Replace the relevant current-state lines in place. Never append history there.
History is append-only in debrief-history.log. Check for duplicate tasks before adding one.
Route in company mode
Use the top-level operating system, not project folders:
- summary and filing record:
operating-system/DEBRIEF_LOG.md - decisions:
operating-system/DECISIONS.md - open tasks:
operating-system/GLOBAL_TASKS.md - waiting on others:
operating-system/WAITING_FOR.md
If one of these files is missing and its template exists in operating-system/templates/, include creation from that template in the plan. Never replace an existing file. List durable brain facts as a separate proposed update to the relevant brain/ file and require separate approval before changing it.
Do not create another meeting-note file when the supplied source is already a note file. Draft follow-ups in the response. Never send them.
Approval gate
Before writing, show:
- every file you plan to touch
- the exact kind of change for each file
- any sensitive or uncertain item that needs a decision
- any follow-up as a clearly labelled draft
Wait for approval. Write only the approved changes. If approval excludes a file or item, do not write it elsewhere. After writing, report what changed and what remains unresolved.
Scaling to per-project folders
Company mode deliberately uses one top-level set of operating-system files. If the system later becomes too busy, you can create project folders with their own DECISIONS.md, WAITING_FOR.md, and meeting files, then change this routing rule. Make that change only after the top-level workflow has proved useful.
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.