using-vibekit

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill. Subagents follow their RTCO brief, not the orchestration discipline. </SUBAGENT-STOP> <EXTREMELY-IMPORTANT> If you think there is even a 1% chance a vibekit skill applies to what you are about to do, you MUST invoke it via the Skill tool. This is not negotiable. You cannot rationalize "the task is too small," "I already know the answer," or "it would be faster to just do it." Skipping a guardrail skill is the failure mode this plugin exists to prevent. </EXTREMELY-IMPORTANT> ## Instruction priority 1. **User's explicit instructions** (CLAUDE.md, AGENTS.md, GEMINI.md, direct messages) — highest. 2. **Vibekit skills** — override default behavior where they conflict. 3. **Default system prompt** — lowest. If the user says "skip the brainstorm" or "just write the code," follow the user. Otherwise, follow the trigger map below. ## Auto-trigger map | Trigger condition | Skill that MUST fire | |---|---| | User says "vibe" or gives a short intent ("add X", "build Y", "fix Z") | `vibe` | | About to start any creative or implementation work, before code is written | `brainstorm-lean` | | Spec is approved, implementation has not started | `plan-write` | | Plan is approved, before any implementation dispatch | `isolate` | | About to dispatch any subagent / Task / Agent call | `brief-compiler` (compile RTCO brief first) | | Executing an approved plan task-by-task | `exec-dispatch` | | ...