Debrief
- 44 installs
- 3.2k repo stars
- Updated August 2, 2026
- davepoon/buildwithclaude
End-of-session ritual that writes a session log plus project status and granular MCP captures, an alias for /handoff.
About
Runs the same end-of-session ritual as /handoff, writing a narrative session log, project-status file, and granular memory captures via the Origin MCP. A developer uses it to preserve session state before closing, preferring the brief/debrief naming pair.
- Identical behavior to /handoff, existing only for symmetric /brief to /debrief naming
- Produces a session log, status file, and per-decision MCP captures
Debrief by the numbers
- 44 all-time installs (skills.sh)
- Ranked #1,687 of 3,280 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davepoon/buildwithclaude --skill debriefAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 44 |
|---|---|
| repo stars | ★ 3.2k |
| Last updated | August 2, 2026 |
| Repository | davepoon/buildwithclaude ↗ |
What it does
End-of-session ritual that writes a session log plus project status and granular MCP captures, an alias for /handoff.
Files
/debrief
Alias for /handoff. Identical behavior — full end-of-session ritual: git context grab (if repo), narrative session log at ~/.origin/sessions/, project status update, granular MCP captures.
Run the steps in /origin:handoff exactly. Same artifacts, same guardrails. The only reason this skill exists is the symmetric naming — /brief (session start) ↔ /debrief (session end). Pick whichever verb feels natural; both invoke the same flow.
When to use
- User says "wrapping up", "let's call it", "we're done", "debrief".
- Session about to close and useful state would otherwise be lost.
When NOT to use
- Mid-flow capture during work → use
/capture(single memory). - Search / lookup → use
/recall.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k