behavioral-modes

Define explicit operational modes with distinct behaviors and outputs, then map request signals to each mode. This Skill provides eight modes — DISCOVER, PLAN, BUILD, REVIEW, DEBUG, TEACH, ORCHESTRATE, and SHIP — with a selection table that activates the right mode from cues in the user's request.

Mode leakage occurs when behaviors from one mode bleed into another, such as writing code during a review or guessing fixes while debugging. Prevent it with explicit anti-leakage rules: state findings without rewriting code, verify hypotheses before proposing fixes, and withhold plans until questions are answered.

Mode selection uses a signal table mapping request phrases to modes. For example, "how does" or "explain" triggers TEACH, tracebacks trigger DEBUG, "review this" triggers REVIEW, "build" or "implement" triggers PLAN then BUILD, and multi-domain requests trigger ORCHESTRATE.

Use DEBUG mode when something is broken and the root cause is unknown. It enforces forming a hypothesis first, testing one variable at a time, and documenting outcomes, producing a root cause statement and minimal fix rather than a guessed workaround.

Yes, ORCHESTRATE mode handles multi-domain requests by identifying involved domains, activating appropriate specialist perspectives in sequence, and synthesizing outputs into a coherent result while ensuring consistency across boundaries like API contracts.