fest-execution: Keep Agent Workflows Moving with Festival Traceability

Where this fits

You're an agent working through a festival backlog. You finish a task, but the next step is ambiguous: should you mark it completed, advance a workflow gate, or commit with traceability? Without a disciplined loop, you lose sequence context and break the project's audit trail. fest-execution gives your agent a clear, repeatable protocol for task state, commits, and validation.

Why agents benefit

• Deterministic task progression: fest next returns the exact next actionable task, removing guesswork from multi-step workflows.
• Explicit state transitions: fest task completed|blocked|reset lets you signal outcomes precisely—no ambiguous statuses or skipped steps.
• Traceable commits: fest commit ties every code change to a festival task, creating an audit trail that humans and agents can follow.
• Workflow gate validation: fest validate confirms sequence progress, catching skipped phases before they cause downstream failures.
• Shell integration: fgo toggles between festival and project directories, enabling smooth context switching without manual path juggling.

Practical scenarios

Handling blocked tasks with reasons

You're mid-sprint and a dependency is missing. Instead of stalling, you run fest task blocked --reason "Waiting on API credentials". The agent records the block, the reason is stored, and fest next skips to a task you can actually complete—keeping momentum without losing context.

Committing after a completed feature

You finish implementing a feature. The loop says: fest task completed then fest commit. The commit message auto-includes the task ID, so the project history maps directly to festival items. Later, fest validate confirms the current step is satisfied, and the workflow advances cleanly.

Relinking after a repo move

Your project directory changes (new worktree, moved repo). You run fest link /new/path and fest link --show to verify. Without relinking, every fest command fails silently—this skill catches that early, saving debugging time.

Add it to your agent workflow

Install the skill with:

npx skills add Obedience-Corp/festival --skill fest-execution

Then, in your agent's skill configuration, expose it for tasks that involve festival execution. A minimal usage pattern:

fest next
# ... do work ...
fest task completed
fest commit
fest validate

For more context, see the fest-execution skill page.

Compare before adopting

Before fully integrating, compare against alternatives: check if the festival project is actively maintained (look at commit recency and issue resolution), whether the skill's command set matches your workflow's complexity, and if you already have a task-tracking loop that this would duplicate. Also verify the shell integration works in your agent's runtime environment.

Why it is worth tracking

With 46 stars and a focused scope, fest-execution shows early community interest in structured task execution for agents. Its strength lies in enforcing a tight loop that reduces ambiguity. Keep an eye on it if you need traceable, sequence-aware task automation—evaluate when your projects demand stricter auditability or when you're building multi-step agent pipelines that benefit from explicit state transitions.