debrief
Skill1 starsChanged 5 months agoApache-2.0View on GitHub
Capture decisions, learnings, and feedback from the current session into memory/{decisions,learnings,feedback}.md. Use this whenever the user types /debrief, says "let's note what we decided" / "capture this" / "save this for next time", finishes a substantive session worth remembering across sessions, or wants to file a discrete decision with rationale. Single-agent personal version (vs cortex /debrief which is OACP-multi-agent).
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
- Works-HQ/ai-brain-starter-packtheir 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
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
- Works-HQ/ai-brain-starter-pack★ 3same name
- armenr/modelmux★ 2same name
- siemendev/release-process★ 2same 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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
When the user runs /debrief, do the following:
- Distinctive: line 69
Don't push unless the user asks.
- Distinctive: line 74
Don't fabricate. If a "learning" is actually just routine work, don't promote it.
- Distinctive: line 75
If there's nothing to capture, say so: "No new entries this session."
“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 — Session Capture
Pull decisions, learnings, and feedback out of a session and into memory.
Instructions
When the user runs /debrief, do the following:
1. Identify session content
Review what was discussed this session. Look for three categories of capturable content:
- Decisions: choices made that will affect future behavior (e.g., "we'll use X instead of Y", "stop doing Z")
- Learnings: operational knowledge discovered (tool gotchas, workflow insights, patterns that worked or failed)
- Feedback: corrections or confirmed approaches the user gave you ("don't do X", "yes exactly, keep doing that")
2. Propose decisions.md entries
For each decision, propose an entry:
## YYYY-MM-DD: [short title]
**Decision**: [what was decided]
**Why**: [reasoning]
**Notes**: [anything else relevant]Show each proposal to the user. Apply only what they confirm.
3. Propose learnings.md entries
For each learning, propose an entry under the appropriate section (Workflow / Tools / Patterns):
- [short title]: [what was learned, in one or two lines]Show, confirm, apply.
4. Propose feedback.md entries
For corrections or confirmed approaches, propose:
## [short rule]
**Why**: [the reason the user gave]
**How to apply**: [when this kicks in]Include the why — it lets future-you judge edge cases.
5. Apply with confirmation
Apply each confirmed entry. Skip ones the user vetoes.
6. Commit
Stage updated memory files and commit:
debrief: YYYY-MM-DD — N decisions, M learnings, K feedbackDon't push unless the user asks.
Notes
- Be selective. Not every session has decisions worth capturing. Skip silently if there's nothing real.
- Don't fabricate. If a "learning" is actually just routine work, don't promote it.
- If there's nothing to capture, say so: "No new entries this session."
- This skill is for substantive sessions — quick chats don't need a debrief.
Learned from runs
(empty — populated as the skill is used)
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.

