From batch
Pause implementation to discuss architecture, alternatives, or understanding. Use when you want to step back and discuss before coding. Checkpoints context to active bead for safe resumption.
How this skill is triggered — by the user, by Claude, or both
Slash command
/batch:discussThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Keywords**: discuss, pause, architecture, alternatives
Keywords: discuss, pause, architecture, alternatives
| Command | Action |
|---|---|
/discuss <topic> | Checkpoint → enter discussion mode |
/discuss continue | Restore context → resume implementation |
/discuss end | Synthesize insights → update bead → resume |
/discuss history | Search past discussions via recall |
/discuss <topic> — Startgit status --short, git diff --stat, current step, metrics), prepend checkpoint to issue notes:
## Discussion checkpoint (YYYY-MM-DD)
- Working tree: <files>
- Current step: <what was being done>
- Last metric: <benchmarks if applicable>
- Next action: <what to do when resuming>
Context checkpointed to <issue-id> (<title>). Ready to discuss: <topic>.No active tracking issue — discussing freely. /discuss end to capture insights.Discussion mode rules:
file:line refs, read actual files/discuss end summary/discuss end first/discuss continue — Resumegit status --short + git diff --stat — check working treeResuming
<id>: Checkpoint: Working tree: Next:
/discuss end — Wrap Up & Resume## Discussion: <topic> (YYYY-MM-DD)
- Key insight: <main takeaway>
- Decided: <decisions>
- Impact: <changes to approach, or "none">
/discuss continue)./discuss historybun recall "discuss" --since 2w
bun recall "<specific-topic>" --since 2w
/discuss end, not bare /discuss continue, after deep discussionsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub beorn/bearly