vibe-modelisted

# Vibe Mode Skill Sets and persists the execution mode for the entire vibe-* framework. One command. Affects every skill in the session. --- ## Commands ``` vibe-mode: autonomous ← full auto-execution, subagents, auto-review vibe-mode: manual ← default, waits for next and review: at each step vibe-mode: status ← shows current mode and what it means ``` --- ## Step 1 — Read current CLAUDE.md ```bash cat CLAUDE.md 2>/dev/null | grep "VIBE_MODE" || echo "NOT SET" ``` If `CLAUDE.md` does not exist: > "No CLAUDE.md found — are you at the project root? > Run this from inside a vibe-* project." Stop. --- ## Step 2 — Apply the mode ### Setting autonomous mode Find the `## Execution mode` section in `CLAUDE.md`. If it exists — update the `VIBE_MODE` line. If it doesn't exist — append the section. ``` ## Execution mode VIBE_MODE=autonomous ``` Then confirm: ``` ⚡ Autonomous mode activated. What this means for this session: Tasks — execute automatically, no "next" needed Parallel — independent tasks spawn as subagents simultaneously Sequential — dependent tasks run in order automatically Review — runs automatically after each phase completes P0 found — stops and waits for you to resolve P1/P2 — logged to backlog, build continues Deploy — always manual, no exceptions To switch back: vibe-mode: manual ``` ### Setting manual mode ``` ## Execution mode VIBE_MODE=manual ``` Confirm: ``` ✋ Manual mode activated. What t