How do I install the Fest Execution skill?

Run npx skillmds@latest add obedience-corp/fest-execution-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fest Execution safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fest Execution?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fest Execution free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fest Execution?

Obedience-Corp (@obedience-corp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fest Execution by obedience-corp — Agent Skill

Name: Fest Execution
Author: Obedience-Corp

File contents

Festival Execution

Core Loop

fest next → do work → fest task completed|blocked → fest commit → fest validate → repeat

Link + Navigation

Festival commands from a project directory depend on an active festival-project link.

# In festival directory: link the execution project path
fest link /absolute/path/to/project
fest link --show

# Shell navigation (after `eval "$(fest shell-init zsh)"`)
fgo           # toggle festival ↔ linked project
fgo project   # jump to linked project
fgo fest      # jump back to linked festival

If the execution project path changes (moved repo, new worktree), relink before continuing work.

Task State

fest task completed
fest task blocked --reason "..."
fest task reset

Do not mix command families:

fest task mutates task status.
fest workflow advances phase-level workflow/gate steps.

Visibility and Dependencies

fest show --inprogress --watch
fest show --roadmap
fest deps

Workflow Steps (Phase-Level)

fest workflow status
fest workflow advance
fest workflow skip --reason "..."

Lifecycle Hooks

Task state changes can fire configured hooks. Inspect the effective set before assuming a transition is inert:

fest hooks list

Verbs: task_start, task_complete, sequence_complete, phase_complete, gate_approve.

task_start fires on the first transition into work, whichever surface causes it: fest status set in_progress --task <id>, a direct completion, or the first fest task update <percent> above zero. Resuming or re-marking in progress never re-fires it; fest task reset clears the recorded start.
task_complete fires on every completion surface, not just fest task completed.

Task document frontmatter binds names only. Bare pre/post bind around the terminal verb; the nested start: stage binds around task_start and is honored on task documents only.

hooks:
  pre: [lint]
  post: [approval_judge]
  start:
    pre: [anchor]

A fail: closed pre-hook blocks the transition and leaves the task untouched.

Validation

fest validate
fest validate <festival-path>

Common Mistakes

Using fest task complete / fest task block (wrong verb forms: use completed / blocked).
Confusing fest workflow commands with task-status commands.
Continuing work from a new project path without rerunning fest link.
Skipping fest next and manually selecting tasks out of dependency order.
Putting a start: hook stage on a goal document: task_start never fires there and fest validate warns about it.

---name: fest-execution-2description: 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.---# Festival Execution## Core Loop```textfest next → do work → fest task completed|blocked → fest commit → fest validate → repeat```## Link + NavigationFestival commands from a project directory depend on an active festival-project link.```bash# In festival directory: link the execution project pathfest link /absolute/path/to/projectfest link --show# Shell navigation (after `eval "$(fest shell-init zsh)"`)fgo # toggle festival ↔ linked projectfgo project # jump to linked projectfgo fest # jump back to linked festival```If the execution project path changes (moved repo, new worktree), relink before continuing work.## Task State```bashfest task completedfest task blocked --reason "..."fest task reset```Do not mix command families:- `fest task` mutates task status.- `fest workflow` advances phase-level workflow/gate steps.## Visibility and Dependencies```bashfest show --inprogress --watchfest show --roadmapfest deps```## Workflow Steps (Phase-Level)```bashfest workflow statusfest workflow advancefest workflow skip --reason "..."```## Lifecycle HooksTask state changes can fire configured hooks. Inspect the effective set beforeassuming a transition is inert:```bashfest hooks list```Verbs: `task_start`, `task_complete`, `sequence_complete`, `phase_complete`,`gate_approve`.- `task_start` fires on the **first** transition into work, whichever surface causes it: `fest status set in_progress --task <id>`, a direct completion, or the first `fest task update <percent>` above zero. Resuming or re-marking in progress never re-fires it; `fest task reset` clears the recorded start.- `task_complete` fires on **every** completion surface, not just `fest task completed`.Task document frontmatter binds names only. Bare `pre`/`post` bind around theterminal verb; the nested `start:` stage binds around `task_start` and ishonored on task documents only.```yamlhooks: pre: [lint] post: [approval_judge] start: pre: [anchor]```A `fail: closed` pre-hook blocks the transition and leaves the task untouched.## Validation```bashfest validatefest validate <festival-path>```## Common Mistakes- Using `fest task complete` / `fest task block` (wrong verb forms: use `completed` / `blocked`).- Confusing `fest workflow` commands with task-status commands.- Continuing work from a new project path without rerunning `fest link`.- Skipping `fest next` and manually selecting tasks out of dependency order.- Putting a `start:` hook stage on a goal document: `task_start` never fires there and `fest validate` warns about it.

Frequently asked questions

Fest Execution