vibe-modelisted

Sets the execution mode for the vibe-* framework — manual or autonomous — plus who approves the spec and design (APPROVALS) and whether an autonomous build continues past a passed phase gate (PHASES). `vibe-mode: run` resumes a build from the files alone — the single entry point for driving vibe headlessly (e.g. `claude -p`). In manual mode: waits for "next" between tasks, waits for "review:" after phases. In autonomous mode: executes all tasks automatically, uses subagents for independent tasks in parallel, auto-runs review after each phase and clears a failing gate with up to 2 fix cycles, and stops only when a gate is still blocked, a task fails twice, an approval is needed, or at deploy. Every stop is written to vibe/.run_state.json. Triggers on "vibe-mode: autonomous", "vibe-mode: manual", "vibe-mode: status", "vibe-mode: run", "vibe-mode: approvals", "vibe-mode: phases", "continue the build", "set autonomous mode", "set manual mode", "switch to autonomous", "turn on autonomous", "turn off autonomous", "
aakashdhar/vibe-skill · ★ 7 · Web & Frontend · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Mode Skill Sets and persists how the vibe-* framework runs, and resumes a build. The full contract for running without a person watching is [`references/HEADLESS.md`](references/HEADLESS.md). --- ## Commands ``` vibe-mode: autonomous ← full auto-execution, subagents, auto-review vibe-mode: manual ← default, waits for next and review: at each step vibe-mode: approvals human ← default: you sign off the spec and the design vibe-mode: approvals auto ← the agent signs them off (logged in DECISIONS.md) vibe-mode: phases stop ← default: stop after each passed phase gate vibe-mode: phases continue ← carry on into the next phase automatically vibe-mode: status ← shows the current settings and what they mean vibe-mode: run ← resume the build from where the files say it is ``` All settings are read with one helper (env vars `VIBE_MODE`, `VIBE_APPROVALS`, `VIBE_PHASES` override CLAUDE.md, so a driver can set them before CLAUDE.md exists): ```bash VS="$HOME/.claude/skills/vibe-mode/scripts/vibe_state.py" python3 "$VS" mode ``` --- ## Step 1 — Read current CLAUDE.md ```bash python3 "$VS" mode ``` If `CLAUDE.md` does not exist and the command is anything other than `status` or `run`: > "No CLAUDE.md found — are you at the project root? > Run this from inside a vibe-* project." Stop. --- ## Step 2 — Apply the setting All three settings live in one section of `CLAUDE.md`. Find `## Execution mode`; if i