Explore skills

Save current work progress to .bdk/save-progress/ for resuming in a future session. Use when context is large, work is in progress, and you want to stop and continue later.

Coordinator that executes a plan in parallel groups via background subagents. Spawns implementers, then dedicated test-runner / static-analyse subagents, then routes failures back to the original implementer (SendMessage) or a fresh fixer. Fully autonomous — no human-in-loop.

Use when existing architecture documentation needs refreshing after code changes, when running periodic doc maintenance, or when user asks to "update docs", "refresh documentation", or "sync docs with code".

Verify implementation plans before execution using a 4-agent pipeline. Use when you have a written plan (from /bdk:create-plan or manual) and want to check if it will actually work before writing code.

Use for guided Fizzy.do workflows: "set up Fizzy", "configure Fizzy for this project", "sync my work to Fizzy", "review my Fizzy progress", "end of session cleanup". Provides step-by-step guidance for common operations.

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\"

Repo-wide or subsystem-wide architecture hygiene pass that surfaces deepening opportunities, shallow modules, leaky seams, and ownership drift. Default mode is report-only: no bead creation or execution unless explicitly requested.

Use when starting work in an unfamiliar repository, resuming after lost context, or when the user asks to bootstrap repo understanding before implementation.

Use before feature work only when the design is still unclear — for shaping vague product intent, comparing possible feature shapes, and turning fuzzy requests into a documented, approved spec before exploring or planning begins. Do not use this when the feature intent is already clear and the remaining work is to lock implementation decisions; that belongs to pulse:exploring. Trigger phrases: des

Use after completed Pulse work when the user asks to capture post-cycle machine-readable learnings for future planning and execution.

Use when the user asks to distill accumulated dev-notes into reader-facing topic knowledge, rather than to capture a new note or update machine memory.

Use only when the user explicitly asks to save, note, record, or preserve one learning from the current conversation as a raw developer note.