@obedience-corp/fest-execution
BExecute 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.
Install
agr install @obedience-corp/fest-execution --target claudeWrites 1 file into .claude/skills/, pinned to git-2a977809.
- .claude/skills/fest-execution/SKILL.md
Document
name: fest-execution description: 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
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 taskmutates task status.fest workflowadvances 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 "..."
Validation
fest validate
fest validate <festival-path>
Common Mistakes
- Using
fest task complete/fest task block(wrong verb forms — usecompleted/blocked). - Confusing
fest workflowcommands with task-status commands. - Continuing work from a new project path without rerunning
fest link. - Skipping
fest nextand manually selecting tasks out of dependency order.
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-2a977809e1682026-07-31