quanpersie2001

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 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 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 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\"

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 after planning and before execution to verify approved current work is reality-fit, feasibility-ready, and explicitly approved at Gate 3.

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 execution completes when the user needs final quality verification and release-readiness review before closeout.

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\"

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