메뉴
Plan and scaffold festivals. Use when creating festival/phase/sequence/task structure, enforcing naming rules, linking festivals to projects, and promoting lifecycle states.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
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`.
Manage campaign submodule projects. Use when committing inside `projects/*`, deciding status/pull/push scope (root vs submodule vs all), or creating/removing project worktrees.
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`.
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.
| name | fest-planning |
| description | Plan and scaffold festivals. Use when creating festival/phase/sequence/task structure, enforcing naming rules, linking festivals to projects, and promoting lifecycle states. |
fest understand methodology
fest understand structure
fest understand tasks
fest understand rules
fest types festival
NNN_UPPER_CASE/ (e.g., 001_IMPLEMENT/)NN_lower_snake_case/ (e.g., 01_auth_module/)NN_lower_snake_case.md (e.g., 01_create_handler.md)Every sequence should include SEQUENCE_GOAL.md.
Use fest types festival / fest types festival show <type> as source of truth.
standard: Full planning + implementation (recommended for most work)implementation: Execution-only (use when requirements already exist)research: Investigation and explorationritual: Recurring processesfest create festival --name "<name>" --type standard
fest create festival --name "<name>" --type implementation
fest create festival --name "<name>" --type research
fest create festival --name "<name>" --type ritual --dest ritual
planning: Workflow phase for architecture/decisions (WORKFLOW.md, no numbered sequences)research: Investigation and findingsingest: Normalizing incoming context/specsimplementation: Sequence-driven coding (numbered sequences/tasks, quality gates)review: Freeform acceptance/signoffnon_coding_action: Operational actionsfest create phase --name "001_IMPLEMENT" --type implementation
fest create festival
fest create phase
fest create sequence
fest create task
fest promote
fest validate
fest link [path]
fest link --show
fest links
fest unlink
# Shell helper after eval "$(fest shell-init zsh)"
fgo
fgo project
fgo fest
fest scaffold from-plan --plan STRUCTURE.md --name my-festival
For a short, repeatable step checklist that does not need a full festival
(phases/sequences/tasks), scaffold a standalone WORKFLOW.md instead:
fest create workflow <name>
# or, equivalently:
fest workflow create <name>
Both accept --steps '<json>' / --steps-file <file> for agent mode,
--type for the standalone workflow type, and --no-init for advanced mode
(skip runtime init and lazily bootstrap a tracked run on first
fest workflow advance). See the fest-standalone-workflows skill for the
full step-JSON schema and execution loop. Reach for a full festival instead
when the work needs multi-phase planning, sequencing, or quality gates.
fest link --project ... (invalid flag).implementation type when requirements are still unclear.P1-..., S1-...).fest scaffold base command as if it performs generation by itself.