vibe

# Vibe Governed Runtime `vibe` is a host-syntax-neutral skill contract. `/vibe`, `$vibe`, and agent-invoked `vibe` all mean the same thing: enter the same governed runtime, not different runtime authorities. ## What `vibe` Does `vibe` is the official governed runtime for tasks that need: - requirement clarification before execution - one-shot autonomous execution with retained governance - multi-step planning and implementation - multi-agent XL orchestration - proof, verification, and mandatory cleanup This runtime still has one canonical authority: `vibe`. Hosts may expose discoverable labels such as: - `Vibe` - `Vibe: What Do I Want?` - `Vibe: How Do We Do It?` - `Vibe: Do It` Those labels are presentational launch surfaces only. They do not create a second runtime. The user does not choose between `M`, `L`, or `XL` as entry branches. Those grades still exist, but only as internal execution strategy, with only `--l` and `--xl` allowed as lightweight public grade-floor overrides. ## When To Use Use `vibe` when the task is not a trivial one-line edit and you want the system to: - inspect the repo and active skeleton first - clarify or infer intent before building - freeze a requirement document - generate an XL-style execution plan - execute in phases with explicit verification - clean up phase artifacts and managed node residue Do not use `vibe` for: - casual Q and A - simple explanation-only requests - tiny edits where governed overhead is unnecessary ## Uni...