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 when implementing approved Pulse beads, either as a swarm worker or as a single worker when swarming is unavailable.
Use before implementation planning when feature intent is clear but implementation decisions are still unresolved, and the user needs those decisions locked first.
Use after pulse:exploring when locked decisions are ready and the user needs a mode-gated plan with an approved work shape and current-work prep for validation.
Use when starting any Pulse workflow, resuming a Pulse session, or before planning or execution when tool readiness or onboarding state may block the flow.
Use after execution completes when the user needs final quality verification and release-readiness review before closeout.
Use after pulse:validating approves execution and swarm mode is recommended, when the current work slice should be run by coordinated parallel workers.