Explorar skills

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.

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.

Design and iterate on logos using SVG. Use this skill when the user asks to "create a logo", "design a logo", "make me a logo", "iterate on this logo", "logo for my project", or discusses logo design, branding icons, or wordmarks.

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.

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.