{"slug": "festival-a-vibe-engineering-framework", "title": "Festival: A Vibe Engineering Framework", "summary": "Obedience-Corp released Festival, an open-source \"vibe engineering\" framework that lets developers configure agent workflows so a stated goal is planned and executed step by step via the `fest next` command, with plans, checks, and commits persisted in files and Git. Festival installs the `camp`, `fest`, and `festival` tools via Homebrew (`brew install --cask Obedience-Corp/tap/festival`) or npm (`npm install -g @obedience-corp/festival`), and works with Claude Code, Codex, Grok Build, Cursor, OpenCode, or any agent that can read files and run commands. The project points to a CodeSignal Practice Simulator demo built from three completed festivals, with plans, tasks, review findings, and verification evidence included in the repository.", "body_md": "**Festival is a vibe engineering framework.**\n\nYou configure it to your specific workflows and processes. When it plans and executes, the work is done the way you want it done.\n\nYou describe a goal in a sentence. Your agent plans that goal inside the workflows you set up, and `fest next` runs the next step. The plan, the checks, and the commits stay in files and Git when the session ends.\n\nA camp is where that configuration lives. A festival is one long goal inside it. Use it with Claude Code, Codex, Grok Build, Cursor, OpenCode, or another agent that can read files and run commands.\n\n[Get started](#get-started) · [Explore the demos](#explore-the-tools) · [Video quick start](https://docs.fest.build/getting-started/quickstart/) · [Website](https://fest.build/) · [Discord](https://discord.gg/Rt7dDY6VqD) · [简体中文](https://github.com/Obedience-Corp/festival/blob/main/README.zh-CN.md)\n\nThree completed festivals built the [CodeSignal Practice Simulator](https://github.com/Festival-Examples/codesignal-practice-simulator).\nAgents followed the `fest next` loop, with testing and review gates feeding\nfindings back into fixes. The demo repository includes the plans, tasks,\nreview findings, and verification evidence for each build.\n\n[Explore the demo](https://github.com/Festival-Examples/codesignal-practice-simulator) ·\n[Inspect the three festivals](https://github.com/Festival-Examples/codesignal-practice-simulator/tree/main/festivals) ·\n[Watch all three replays](https://github.com/Festival-Examples/codesignal-practice-simulator#how-this-was-built)\n\n[Try your own handoff](#get-started), or star this repository to keep it handy.\n\nStart with a real outcome that you can review. For example:\n\n- **A feature across repositories:** “Add account deletion to the API and web app. Cover it with tests and document how existing users are affected.”\n- **An investigation before a build:** “Investigate why this service slows down under load. Save the evidence, compare the options, and bring me a recommendation before changing production.”\n- **A recurring review:** “Review this week's dependency changes, flag compatibility risks, and prepare the updates for my approval.”\n\nThe goal, constraints, and success criteria come from you. Your agent works through the plan and returns when it reaches a review point or a decision that needs you.\n\n[Explore the use cases](https://docs.fest.build/use-cases/) · [See example camps and festivals](https://github.com/Obedience-Corp/examples)\n\nChoose one method. Both install `camp`, `fest`, and the `festival` manager. Git is required.\n\n**macOS with Homebrew**\n\n```\nbrew install --cask Obedience-Corp/tap/festival\n```\n\n**macOS or Linux with Node.js**\n\n```\nnpm install -g @obedience-corp/festival\n```\n\nThen check the install:\n\n```\nfestival doctor\n```\n\n[Linux packages, WSL2, and other install methods](https://docs.fest.build/getting-started/installation/). Native Windows support is being hardened; use WSL2 for now.\n\nA **camp** holds the context for one part of your life: your job, a side project, or a hobby. It can contain several projects, along with their research, plans, and decisions.\n\nAfter installing, create a camp:\n\n```\ncamp create my-camp\ncamp create work\ncsw my-camp\ncsw work\n```\n\n`camp create` puts each camp in `~/campaigns/` and asks for a description and mission. `csw` is the shorthand for `camp switch` and moves your shell from one camp to the other. Add the [shell integration](https://docs.fest.build/getting-started/shell-setup/) so the shorthand exists. With no name, `csw` opens the picker.\n\nOne recording, in a fresh demo home. On your machine the camps are at `~/campaigns/my-camp` and `~/campaigns/work`.\n\nIf an agent is already open, paste this. It installs Festival when `camp` is missing, updates `camp`, `fest`, and `festival` together, creates the camp, and adds the shell hook. Open a new terminal and run `csw <name>` to enter the camp.\n\n```\nIf `camp` is missing, install Festival, then run `festival doctor`. On macOS with Homebrew, use `brew install --cask Obedience-Corp/tap/festival`. On macOS or Linux with Node.js, use `npm install -g @obedience-corp/festival`.\n\nTo update camp, fest, and festival together, run `festival update`. Do not pass `--force`.\n\nAsk me for a camp name, a one-line description, and a mission. Create the camp with `camp create <name> -d \"<description>\" -m \"<mission>\"`. The camp is at `~/campaigns/<name>`. Read `camp create --help` before adding flags. Use `camp create` for this. Do not run `camp init` or `festival setup`.\n\nAfter Festival is installed, add the shell hook with the installer. Detect my shell and run one of `festival shell-init zsh --append --yes`, `festival shell-init bash --append --yes`, or `festival shell-init fish --append --yes`. Pass `--yes`. Without it, and with no terminal to answer, the installer writes nothing. The command skips the edit when the hook is already there. Then tell me to open a new terminal and run `csw <name>`. You can keep working in `~/campaigns/<name>`.\n\nSkills are optional. The CLI can teach you the workflow.\n```\n\nOpen your coding agent at that camp root. The [agent setup guides](https://docs.fest.build/getting-started/agents/) cover skills and integrations for your tool. Skills are optional; the CLI can teach your agent the workflow.\n\nLink a repository you already use. Replace the path with its full local path:\n\n```\ncamp project link /path/to/your-existing-repo\n```\n\nYour repository stays where it is. Camp links it under `projects/` and adds a `.camp` attachment file to the repository. You can also [clone a project into the camp](https://docs.fest.build/cli-reference/camp/camp_project_add/).\n\nA **festival** is the structured plan and work record for a goal. Tell your agent what you want done and ask it to create a festival for the work:\n\nI want [what you want done]. Create a festival for it and run the `fest next` loop.\n\nA real Grok Build session planning a sample app feature. The agent handles the planning commands; you review the proposed work.\n\nYour agent handles planning and execution, asking you when it reaches an approval point or needs a decision. You can focus on other work and review the results when they're ready.\n\nTo check progress along the way, open another terminal in the festival directory and run `fest watch`.\n\nThe progress view you can open alongside your agent. This recording demonstrates the real `fest watch` interface with scripted progress updates in a sample festival.\n\n**If the session ends:** point your next agent at the saved festival and ask it to continue from the linked project. The recorded plan, progress, and decisions give it a starting point.\n\n[Follow the video quick start](https://docs.fest.build/getting-started/quickstart/) to see setup, planning with Grok Build, and the progress view.\n\n`fest gif` turns recorded festival progress into a GIF you can send and share:\n\n```\nfest gif my-festival -o replay.gif\nfest gif --festival MF0001 --speed 2\n```\n\nWhen a festival moves to completed, Fest creates `festival-replay.gif` and embeds\nit in `FESTIVAL_OVERVIEW.md`, with both files included in the completion commit.\nUse `fest gif --embed` to refresh it or add a replay to an older festival.\n\nSee the [replay guide](https://docs.fest.build/guides/festival-replays/) for\nexamples, sharing, and recovery.\n\nA festival is a **graph of work**, organized into phases, sequences, and tasks. Each task has context and completion criteria. Your agent uses `fest next` to find the next actionable step, does the work, checks the result, and records progress before continuing.\n\nThat is the basis for **loop engineering** with Festival: repeatable planning, execution, review, and handoff loops. You can start with a lightweight `WORKFLOW.md`, build a full festival for a larger goal, or run separate festivals with agents in separate worktrees.\n\nThe camp holds the context around those goals over the life of the work. Research can inform a design; that design can become a festival; its results and decisions remain available for the next goal.\n\nQuality gates provide places to test and review. `fest validate` checks plan structure, and `fest commit` links commits to festival tasks. You review the actual output and verification evidence before accepting the result.\n\n[Loops & orchestration](https://docs.fest.build/guides/loops-and-orchestration/) · [Festival methodology](https://docs.fest.build/methodology/overview/) · [Work items](https://docs.fest.build/methodology/work-items/)\n\n| Tool | What it handles | \n|---|---|\n| [camp](https://github.com/Obedience-Corp/camp) | Projects, context, navigation, and the work queue across your camp. | \n| [fest](https://github.com/Obedience-Corp/fest) | Goal-based plans, the next-step loop, progress, and review checkpoints. | \n| `festival` | Installing and updating the suite, browsing CLI plugins, and checking your installation. | \n\nRun `festival browse` to explore available CLI plugins. See [suite and plugin management](https://docs.fest.build/getting-started/festival-manager/) for installation, updates, and how CLI plugins differ from agent integrations.\n\n- **Jump straight to the work.**`cgo p api` finds a matching project;`cgo f` takes you to festivals. Add the[shell integration](https://docs.fest.build/getting-started/shell-setup/) to enable these shortcuts.\n- **Switch camps.**`camp switch` moves between registered camps.`csw` is the shorthand.\n- **Find the next thing to pick up.**`camp workitem` brings intents, research, designs, and festivals into one work queue.\n- **Start fresh after a merged PR.**`camp fresh` syncs a project to its default branch and prunes merged branches. Preview with`camp fresh --dry-run` from that project first, including any configured branch creation or follow-up commands.\n\n[Everyday development with cgo and camp fresh](https://docs.fest.build/guides/everyday-development/)\n\nThe GIFs play on this page at a readable size.\n\n## Move between projects, plans, and camps\n\n`cgo` jumps to a project or planning directory. `camp switch` moves between camps, and `csw` is the shorthand.\n\n## See your camps and the projects inside one\n\n`camp list` browses registered camps by org. Move through them, change a camp's status, and filter down to the active ones.\n\n`camp project list` browses the projects in the current camp, grouped by type.\n\n## Find work, capture an idea, and sort the inbox\n\n**Find work across the camp.** `camp workitem` brings intents, research, designs, and festivals into one searchable list.\n\n**Capture an idea.** `camp intent add` saves it to the inbox for later.\n\n**Sort the inbox.** `camp intent explore` lets you browse intents by status and read their details.\n\n## See which festivals are active and inspect a plan\n\n`fest list` groups festivals by status, so you can see what's active, ready, or still being planned.\n\n`fest show` opens the structure of a plan, from its phases down to individual tasks.\n\n## Start fresh after a merged change\n\n`camp fresh configure` sets the follow-up commands that run after a project syncs.\n\n`camp fresh` checks out the default branch, pulls, prunes merged branches, and runs those follow-ups.\n\n## Add testing and review gates to a plan\n\n`fest gates apply` previews the quality gates it will add before applying them with approval.\n\n## Review old work and clear space for what's next\n\n`camp dungeon crawl` walks through stale work so you can choose what to keep or archive.\n\n## Reach a camp on another machine\n\n`camp machine` lists computers camp can hop to, and can add one from your Tailscale network.\n\n## Open the Festival installer\n\n`festival` opens the suite manager: install the tools, check the setup, and launch camp and fest.\n\n## Watch a longer Festival session **(click to expand video preview)**\n\nAn earlier Festival workflow recording at 16× playback speed. Use the setup instructions above for the current first-run path.\n\n[More video walkthroughs and demos](https://docs.fest.build/videos/)\n\n**Can I keep my issue tracker?**\n\nYes. Keep issues where your team coordinates, and use Festival for the agent's plan and work record. Intents and other work items live in files, so scripts or justfiles can connect them to an external service's API. Ask your agent to help build the connection you need. [See the workflow](https://docs.fest.build/compare/festival-vs-issue-trackers/).\n\n**Can I change agents partway through?**\n\nYes. The next agent can read the same saved plan, decisions, and progress. Give it the festival location and access to the linked project. [Agent handoff guide](https://docs.fest.build/use-cases/ai-agent-handoff/).\n\n**Do I need a Festival account?**\n\nThe CLI tools are free to use and run locally without a Festival account. Your agent's account, model costs, and permissions remain with the provider you choose.\n\n- [Join the Obedience Corp Discord](https://discord.gg/Rt7dDY6VqD) : get help with Festival, compare workflows, and share what you build.\n- [Documentation](https://docs.fest.build/) : guides, use cases, and CLI reference.\n- [First festival tutorial](https://docs.fest.build/tutorials/first-festival/) : a hands-on walkthrough of the plan structure.\n- [Examples](https://github.com/Obedience-Corp/festival/blob/main/examples) and[templates](https://github.com/Obedience-Corp/festival/blob/main/templates) : work you can inspect and adapt.\n- [Plugin authoring](https://docs.fest.build/guides/plugin-authoring/) : extend`camp` and`fest` with your own commands.\n- [Report a bug or request a feature](https://github.com/Obedience-Corp/festival/issues) : tell us what happened or what would help.\n- [Give feedback](https://fest.build/feedback/) or[read the blog](https://fest.build/blog/) .\n\n**Festival App is in development.** The CLI tools are available now. [See what's coming](https://fest.build/#app).\n\nIf Festival is useful to you, **star this repository** to help other developers discover it. A bug report, a workflow you share, or an example of work you've handed off helps us improve it.\n\n[Apache License 2.0](https://github.com/Obedience-Corp/festival/blob/main/LICENSE) · Built by [Obedience Corp](https://obediencecorp.com/).", "url": "https://wpnews.pro/news/festival-a-vibe-engineering-framework", "canonical_source": "https://github.com/Obedience-Corp/festival", "published_at": "2026-10-07 22:12:07+00:00", "updated_at": "2026-10-07 22:19:22.300068+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "developer-tools", "ai-products"], "entities": ["Obedience-Corp", "Festival", "Claude Code", "Codex", "Grok Build", "Cursor", "OpenCode", "CodeSignal Practice Simulator"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/festival-a-vibe-engineering-framework", "markdown": "https://wpnews.pro/news/festival-a-vibe-engineering-framework.md", "text": "https://wpnews.pro/news/festival-a-vibe-engineering-framework.txt", "jsonld": "https://wpnews.pro/news/festival-a-vibe-engineering-framework.jsonld"}}