brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
debriefAlias 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.
Independent GitHub snapshot · Automated classification · Original documentation governs
/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"]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.
/capture (single memory)./recall.