debrief

Name: debrief
Author: davepoon

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

by davepoon(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from davepoon/buildwithclaude (plugins/origin/skills/debrief/SKILL.md). Install upstream with npx skills add davepoon/buildwithclaude --skill debrief. Copyright stays with the author.

/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.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/davepoon-buildwithclaude-debrief/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

davepoon-buildwithclaude-debrief.ocm.jsonjson

{
  "ocm": "1",
  "id": "davepoon-buildwithclaude-debrief",
  "kind": "skill",
  "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.",
  "publisher": "davepoon",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "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."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/davepoon/buildwithclaude",
      "path": "plugins/origin/skills/debrief/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/davepoon/buildwithclaude/blob/HEAD/plugins/origin/skills/debrief/SKILL.md",
      "key": "davepoon/buildwithclaude/plugins/origin/skills/debrief/SKILL.md"
    },
    "allowed_tools": [
      "Bash",
      "mcp__plugin_origin_origin__capture"
    ]
  },
  "instructions": "# /debrief\n\nAlias for `/handoff`. Identical behavior — full end-of-session ritual:\ngit context grab (if repo), narrative session log at\n`~/.origin/sessions/`, project status update, granular MCP captures.\n\nRun the steps in `/origin:handoff` exactly. Same artifacts, same\nguardrails. The only reason this skill exists is the symmetric naming —\n`/brief` (session start) ↔ `/debrief` (session end). Pick whichever\nverb feels natural; both invoke the same flow.\n\n## When to use\n\n- User says \"wrapping up\", \"let's call it\", \"we're done\", \"debrief\".\n- Session about to close and useful state would otherwis",
  "cost": {
    "context_tokens": 182
  }
}

Fetch it by URL: GET /api/v1/registry/davepoon-buildwithclaude-debrief/manifest?version=1.0.0