AGENTS.md git:20260711.aa1ff20A

Immutable. This exact content never changes and is served at /api/v1/blob/b7d0fe7f7769e9d1.

<!-- GENERATED by packaging/generate.mjs from claude-plugin/. Do not edit; edit the source and re-run 'just plugin generate'. -->

# Festival

Festival is a goal-oriented project management methodology for human and AI development workflows,
driven by the `fest` and `camp` CLIs. It organizes work as festivals made of phases, sequences,
and tasks, with quality gates between them.

## What ships

- The `fest` and `camp` CLIs, which the session-start hook installs and keeps current.
- 9 skills describing the workflows:

- `camp-navigation`: Navigate campaign workspaces with `cgo` and `camp go`. Use when you need to move between projects/festivals/workflow directories, switch context quickly, or resolve script-safe paths with `camp go --print`.
- `camp-projects`: Manage campaign submodule projects. Use when committing inside `projects/*`, deciding status/pull/push scope (root vs submodule vs all), or creating/removing project worktrees.
- `campaign-commit`: Choose the correct commit command in a campaign workspace. Use when you are about to commit and need to select `camp p commit`, `fest commit`, root `git commit`, or intentional root pointer sync via `camp refs-sync`.
- `campaign-structure`: Orient within campaign directory structure. Use when deciding where work belongs (intents vs festivals vs design vs docs vs dungeon), especially when a task is not yet planned or folder ownership is unclear.
- `campaign-workflows`: Manage campaign intents, dungeons, and flow transitions with `camp`. Use when capturing ideas, promoting intents to festivals, archiving work, or moving workflow items between statuses.
- `fest-execution`: Execute active festival tasks. Use when finding the next task, marking tasks completed/blocked/reset, committing with festival traceability, advancing workflow steps, and validating sequence progress.
- `fest-methodology`: Use when the user mentions festivals, the fest CLI, phases, sequences, or tasks, or when working inside a `festivals/` directory. Provides the core Festival methodology model so Claude understands the planning system.
- `fest-planning`: Plan and scaffold festivals. Use when creating festival/phase/sequence/task structure, enforcing naming rules, linking festivals to projects, and promoting lifecycle states.
- `fest-standalone-workflows`: Create and run lightweight standalone `WORKFLOW.md` loops with `fest create workflow`, `fest next`, and `fest workflow advance`. Use when a user wants step-by-step workflow guidance inside any ordinary directory, explore/design work item, project folder, or thin-start workflow.

## Learn more

Run `fest understand` for the methodology. The multi-harness packaging layout and the
source-of-truth convention are documented in `packaging/README.md`.