debrief
Alias for `/origin:handoff` — symmetric brief/debrief naming. Same status + granular MCP captures. Invoked as `/debrief`. Use when the user prefers the brief/debrief pair over brief/handoff.
npx skills add davepoon/buildwithclaude --skill debrief --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /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 w
What does the debrief skill do?
Alias for `/origin:handoff` — symmetric brief/debrief naming. Same status + granular MCP captures. Invoked as `/debrief`. Use when the user prefers the brief/debrief pair over brief/handoff.
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill debrief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
