Obedience-Corp/fest

Fest CLI

Part of Festival - mission-based AI workspace management. Fest handles hierarchical planning and execution loops; camp handles workspace management. Together they give structure to how you work across multiple projects, contexts, and AI agents.

<p align="center" <a href="https://github.com/Obedience-Corp/fest/stargazers"<img src="https://img.shields.io/github/stars/Obedience-Corp/fest?style=social" alt="Star fest on GitHub"</a </p

<p align="center" <img src="docs/images/banner.jpg" alt="Festival Methodology Banner" width="400" </p

<p align="center" <img src="docs/images/fest-explorer-v3.gif" alt="Fest explorer TUI using the shared Obedience Corp fire palette" width="520" </p

<p align="center"<em<a href="https://github.com/Festival-Examples/example-camp-hardening-festival"See the festival behind this demo &rarr;</a</em</p

Fest is a template-driven agent orchestrator. You describe work as structured documents scaffolded from templates you control, and agents execute them through a tracked loop: fest next hands the agent its next task with full context, quality gates and approval judges check the work, and progress lands in git. Festival Methodology transforms high-level objectives into structured, executable work that AI agents complete autonomously; fest is the CLI that makes it happen.

This practice is loop engineering: instead of babysitting prompts, you design the loop your agents run in (the goals, steps, gates, and feedback) and let them run it. The better your loop, the less you supervise. Fest is a tool for building those loops out of plain markdown.

Install (see the festival repo for all package options):

brew install --cask Obedience-Corp/tap/festival   # macOS/Linux (installs camp + fest)
npm install -g @obedience-corp/festival           # any platform with node

Festivals live within campaigns - isolated workspaces managed by camp. A campaign organizes your projects, plans, and context in one place. See the methodology README for the complete guide.

Your Templates, Your Workflow

Fest ships with a complete default methodology, but the methodology is a template set, not a requirement. Everything fest scaffolds comes from templates you can inspect and change:

• Campaign-level templates - every festival, phase, sequence, and task

document is generated from festivals/.festival/templates/ in your campaign. Edit them and fest uses your versions.

• Custom festival types - festivals/.festival/festivaltypes.yaml

defines which phases each festival type auto-scaffolds. Add your own types for your own workflow shapes.

• Quality gates - defaults included; replace or modify them campaign-wide