Explore skills

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.

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 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 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.

SAP Cloud Application Programming Model (CAP) development skill for the **Node.js runtime only**. Domain-first: prefers CDS schema, annotations, projections, and CAP's generic providers over hand-written handler code ("less code → less mistakes"). Use when the user asks to: build CAP applications, define CDS models, design entities / associations / views / projections, add annotations (validation,

Update the docs/architecture .md spec files after adding a new feature, without re-running the full ms-spec. Detects what changed via git diff, maps changes to the right spec sections, grills the developer for missing context, and patches only the affected .md files. Use when a feature is done and the user wants to keep AI agent context up to date, or says "update spec", "sync spec", "ms-spec-upda

Dynamically discover all git repositories under a parent folder, checkout master/main, and pull latest code. Use when user wants to update all microservices, sync all repos, or says "update-all" or "pull all repos".