القائمة
Execute festival tasks - find next work, track progress, commit with traceability, advance through workflow steps, and validate completion. Use when actively working through a festival's tasks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | fest-execution |
| description | Execute festival tasks - find next work, track progress, commit with traceability, advance through workflow steps, and validate completion. Use when actively working through a festival's tasks. |
The execution loop: find next task, do the work, track progress, commit, validate, repeat.
fest next → read task → do work → fest show --inprogress → fest commit → fest validate → fest next
fest next # Returns the next task with full context
This shows:
Visualize progress with fest show:
fest show --inprogress # Expand only in-progress phases/sequences
fest show --inprogress --watch # Live-updating progress view (recommended)
fest show --roadmap # Full execution roadmap with task statuses
fest show --summary # Aggregate summary stats
fest show --collapsed # Collapsed tree with counters only
fest show --inprogress --watch is the most useful during execution — it continuously refreshes and shows only what you're working on, minimizing noise.
Update task status with fest progress or fest task:
fest progress --task <id> --in-progress # Mark task as started
fest progress --task <id> --complete # Mark task as done
fest task complete # Mark current task as complete
fest task block --reason "..." # Block task with reason
fest commit # Festival-aware git commit
fest commit automatically:
Always use fest commit instead of raw git commit when working on festival tasks.
Some phases use workflow-based execution with defined steps:
fest workflow status # Show current workflow step
fest workflow advance # Move to next step
fest validate # Check structure and completeness
Run after completing each sequence to catch issues early.
fest show --inprogress --watch # Live progress view (primary tracking tool)
fest show # Full festival structure tree
fest status # Entity status details
fest context # Current session context (festival + project)
fest deps # Task dependency graph
Sequences often end with quality gate tasks:
NN_testing.md) - Run tests, verify functionalityNN_review.md) - Code review, architecture checkNN_iterate.md) - Address feedback, fix issuesThese are standard tasks - execute them like any other, but they gate progression to the next sequence.
fest search "auth" # Search festivals by content
fest commits # View commits tied to festival tasks
fest parse <file> # Parse task document into structured data
fest commit - loses progress tracking and traceabilityfest next and picking tasks manually - may miss dependenciesfest validate after completing a sequence - issues compoundfest deps firstUse when working with The Synthesis hackathon official platform API at synthesis.md or synthesis.devfolio.co. Covers agent registration, required humanInfo questions, team and invite-code operations, privacy rules for UUIDs and IDs, official Telegram/community guidance, and handoff to the separate submission workflow.
Participate in the Chainlink Convergence Hackathon — Agents Track. Build and submit one project using the Chainlink Runtime Environment (CRE) via Moltbook. Use when your operator instructs you to enter, build for, or submit to the Chainlink Convergence Hackathon as an autonomous agent.
Enable developers to learn and use Chainlink Runtime Environment (CRE) quickly by referencing filtered CRE docs. Trigger when user wants onboarding, CRE workflow generation (in TypeScript or Golang or other supported languages), workflow guidance, CRE CLI and/or SDK help, runtime operations advice, or capability selection
Navigate campaign workspaces using cgo shell function, camp go, and shortcuts. Use when you need to move between projects, festivals, workflow directories, or any campaign location.
Manage campaign project submodules - add repos, commit with auto-sync, check status, pull/push across projects, and manage worktrees. Use when working with project repositories in a campaign.
Choose the correct commit command in a campaign context. Use before committing code to determine whether to use camp p commit, fest commit, or standard git commit.