Explore skills

Use when the user asks for a manual consolidation pass over runtime artifacts into machine-readable Pulse memory outside the post-cycle compounding flow.

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 when Pulse planning or discovery needs graph-based architecture context, execution-flow tracing, symbol relationships, or blast-radius analysis beyond plain file search.

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 when repository documentation is stale and the user asks to refresh docs to match the current codebase and workflows.

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.

Use when the user asks for root-cause-first debugging of bugs, test failures, flaky behavior, build issues, or integration defects with tracked verification and regression lock-down.

Use when bootstrapping or resuming work in a Pulse project after pulse:preflight, or when a request needs Pulse work-shape/current-work routing and mode-aware skill selection.

Use after planning and before execution to verify approved current work is reality-fit, feasibility-ready, and explicitly approved at Gate 3.

Use when creating a new pulse skill, editing an existing pulse skill, or verifying a skill works under pressure before deploying. Use when you need an agent skill to be bulletproof against rationalization. Do NOT use for project-specific AGENTS.md conventions or one-off solutions.