Festival plugin
Planning framework for coding agents: Fest runs goals through phases, Camp keeps shared context, Obey supervises runs
- 148 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The commit-guard and sync-check hooks hook into commits and agents write plan and context files into your repository
- The Obey background daemon launches agents and works with projects linked to the camp
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/festivalDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The commit-guard and sync-check hooks hook into commits and agents write plan and context files into your repository
- The Obey background daemon launches agents and works with projects linked to the camp
This is third-party code. Review the repository files before installing.
What it does
Festival turns agent work into a process you can inspect and hand off between sessions. You set the goal and success criteria, while plans, decisions, progress and checks live in files and Git. Three parts share the job. Fest runs long goals and automated planning: a festival is made of phases, sequences and tasks, each with context and completion criteria, and the agent finds the next step with fest next. Camp keeps shared context across sessions and projects. Obey launches agents through a background daemon and supervises them. fest validate checks plan structure, fest commit links commits to tasks, and testing and review gates feed findings back into fixes. The agent can be Claude Code, Codex, Cursor, Gemini or opencode: the next agent reads the same plan and continues from where the last one stopped. You can start with one goal in your repository: the README gives a ready prompt for the agent that installs Festival, creates a camp with camp create and links the repository through camp project link. For Obey, after the main install run festival install obey, and ob fest execute --dry-run shows the launch context in advance.
Who it is for. Teams and developers who hand agents long multi-session tasks and want to see the plan, decisions and evidence of the result.
Good fit when
- A task spans several sessions and the next agent must continue from a saved plan
- A feature touches the API and the web app and the work has to be split into phases with review
- Before a change you need an investigation with saved evidence and a recommendation
- You switch agents mid-work and want decisions and progress kept in files
- You need background supervision of agent sessions through Obey and obey top
Not a fit when
- A one-line fix: phase planning will overload the work
- The team only needs an issue tracker: Festival keeps the agent plan and leaves Jira or Linear in place
- The agent works without Git: plans, decisions and commits are tied to a repository
- You need Obey source code: its repository is private and only the binaries are public
Example request
Help me set up Festival for this goal: add account deletion to the API and web app with tests. My repository is at ~/work/shopLimitations
- Git is required; install through Homebrew on macOS, npm install -g @obedience-corp/festival on macOS and Linux or Scoop on Windows x64.
- Windows supports local Camp and Fest work, but camp sync --from, camp clone --from and artifact transfer between camps are unavailable.
- Obey is installed separately with festival install obey, needs a configured provider and model, and its source code is private.
- The shell shortcuts csw, cgo, fgo, fls and cr work only after shell-init is loaded in each shell.
How to disable. npm uninstall -g @obedience-corp/festival removes the package, and Homebrew and Scoop remove the install with their own commands. Campaign files in ~/campaigns and .camp in the repository are deleted manually.
FAQ
How do I install Festival?
Pick one method: brew install --cask Obedience-Corp/tap/festival on macOS, npm install -g @obedience-corp/festival on macOS and Linux or Scoop on Windows x64. Check the install with festival doctor.
How do Fest, Camp and Obey differ?
Fest runs goals and planning, Camp keeps shared context across sessions and Obey launches agents through a background daemon and supervises them.
Which agents work with Festival?
The repository has plugins and skills for Claude Code and Cursor and directories for opencode, Codex and Gemini. You keep your own agent and provider.
Can I keep my issue tracker?
Yes. Issues stay in the team tracker and Festival keeps the agent plan and work record. Intents live in files, so scripts can connect them to a service API.
Do I need a Festival account?
No. The CLI tools run locally and free of charge; your agent account, model costs and permissions stay with the provider you choose.
Discussion
No questions or reviews yet.
Related
PluginsSkills and the porch CLI for agent orchestration: a strong model plans, cheaper ones code, several model families review.
An orchestrator for agents: the workflow is defined in code, every step is enforced, key points need human approval and decisions go into an immutable journal
A team of AI agents from one request: it plans the task, writes code in parallel branches, tests, reviews and opens a pull request
CLI for parallel agents: splits a task into sections, runs Codex, Claude Code or OpenCode together and merges into one branch
An OpenCode plugin that runs a team of parallel agents with separate sessions, a shared task board and messaging
A scaffold of personas, rules and skills in plain Markdown: Maestro hands work to different models and spares your main plan
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Festival (this card) | no | 148 | |
| Planning with Files | no | 28,037 | a skill that keeps a plan in files for one session; Festival adds phases, review gates and shared Camp context |
| Spec-Driven Development | no | 158 | a spec-to-code method; Festival runs goals and passes them between agents |
README in short
The README opens with the idea of vibe engineering and shows a worked example: three festivals built a practice simulator and the demo holds plans, review findings and verification evidence. Then come a diagram of three components, sample tasks to hand to an agent, step-by-step install with a ready prompt, shell setup, Obey background supervision and answers to common questions.