Skip to content

davepoon/buildwithclaude / plugins/origin/skills/debrief

debrief

Verified

Alias for `/origin:handoff` — symmetric brief/debrief naming. Same behavior: end-of-session ritual that writes session log + project status + granular MCP captures. Invoked as `/debrief`. Use when the user prefers the brief/debrief pair over brief/handoff.

FileKindSize
SKILL.mdskill md1.1 KB
---
name: debrief
description: >
  Alias for `/origin:handoff` — symmetric brief/debrief naming. Same
  behavior: end-of-session ritual that writes session log + project
  status + granular MCP captures. Invoked as `/debrief`. Use when the
  user prefers the brief/debrief pair over brief/handoff.
allowed-tools: ["Bash", "mcp__plugin_origin_origin__capture"]
---

# /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`.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall