fest-standalone-workflows
/fest-standalone-workflows
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.
- Author
- obedience-corp ↗
- Repository
- festival ↗
- Licence
- Apache-2.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
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.
Original author description
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.
How it works
- When to Use This vs. a Full Festival
- Create
- Flags
- Step JSON Contract
- Execution Loop
- Common Mistakes
SKILL.md preview
---
name: fest-standalone-workflows
description: 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.
---
# Fest Standalone Workflows
Use a standalone `WORKFLOW.md` when work needs a guided step loop in an ordinary
directory, without setting up a full festival (phases/sequences/tasks).
Thin-start loop:
```text
WORKFLOW.md -> fest next -> do step -> fest workflow advance -> repeat
```
## When to Use This vs. a Full Festival
- **Standalone workflow**: a short, repeatable checklist that can live in any
directory: a code-review checklist, a release-cut runbook, a one-off
investigation. Minimal ceremony, no phases/sequences.
- **Full festival**: multi-phase work that needs planning, sequencing, and
quality gates over an extended effort. Use `fest create festival` instead
(see the `fest-planning` skill).
## Create
Run from the directory that should own the workflow:
```bash
mkdir -p my-workflow && cd my-workflow
fest create workflow my-workflow --steps '{
"title": "My Workflow",
"description": "A lightweight guided loop.",
"steps": [
{
"name": "PLAN",
"goal": "Decide what needs to happen.",
"actions": ["Write the goal.", "List the unknowns."],
"checkpoint": "none"
},
{
"name": "DO",
"goal": "Do the work.",
"actions": ["Make the change.", "Validate it."],
"checkpoint": "verification"
}
]
}'
fest next
```
This scaffolds `WORKFLOW.md`, initializes `.workflow/` runtime state, and
starts a tracked run, so `fest next` works immediately.
`fest workflow create <name>` is an alias of `fest create workflow <name>`
and accepts the same flags. Use whichever noun you reach for first.
For human interactive creation, run the command without `--steps` from a TTY:
```bash
fest create workflow my-workflow
```
It prompts for title, intent, and step lines in `Name|Goal` form.
## Flags
- `--steps '<json>'` / `--steps-file <file>`: agent mode, inline JSON or a
JSON file. See the step schema below.
- `--agent`: strict agent mode (implies `--json`).
- `--type <type>`: standalone workflow type (default `task`).
- `--no-init`: advanced mode. Writes `WORKFLOW.md` only, without initializing
`.workflow/` runtime state or starting a run. `fest next` still works in
this mode, but reports the workflow as not-started; the first mutating
command (`fest workflow advance`) bootstraps a tracked run lazily. Use this
when you want to author the document before committing to a tracked run.
- `--path <dir>` / `--festival <root>`: target a festival phase instead of
standalone mode. Inside a festival phase, or with either of these flags
set, the command writes the phase's `WORKFLOW.md` with no standalone
runtime, so do not pass these when you want a standalone workflow.
## Step JSON Contract
Workflow-level fields:
- `title` (required)
- `description` (optional)
- `steps` (required, non-empty)
Each step needs:
- `name`
- `goal`
Useful optional step fields:
- `actions`
- `output`
- `checkpoint`
Valid checkpoint values:
- `none`
- `verification`
- `documentation`
- `approval_required`
`approval_required` is accepted when the file is created, but standalone
execution cannot advance through blocking approval checkpoints. Use a festival
phase when the workflow needs user-approval gates.
## Execution Loop
```bash
fest next
# do the visible step
fest workflow advance
fest next
```
## Common Mistakes
- Passing `--path` or `--festival` when creating a standalone workflow;
those target a festival phase instead.
- Using `title` inside each step object. Step objects require `name` and
`goal`, not `title`.
- Assuming `--no-init` is required before `fest next` will work. It is not:
the default (no flag) already initializes runtime state and starts a
tracked run in one step.
- Adding `approval_required` to a standalone workflow. The file will validate
at creation time, but `fest workflow advance` cannot cross that blocking
checkpoint outside a festival phase.
Versions
The database has no other skills named fest-standalone-workflows.
Identical content appears in 4 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version be747a860a98 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100fest-methodology
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. - 100fest-execution
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. - 100sprint-loops
Run or resume the Sprint Loops Book v2 workflow when the user explicitly invokes $sprint-loops or directly asks to start, continue, resume, or run a sprint loop. Do not use it for ordinary documentation work or merely because a docs directory exists. - 95steam-store-launch-ops
Turn Steam store-page, wishlist, demo, Next Fest, and launch-window ambiguity into one packet-first Steam launch brief. Use when an indie dev, small studio, founder-marketer, or publisher helper needs to decide whether the next move is a page-promise audit, wishlist-signal… - 100sprint-loop
Run or resume the Sprint Loops Book v2 workflow when the user explicitly invokes /sprint-loop or directly asks to start, continue, resume, or run a sprint loop. Do not use it for ordinary documentation work or merely because a docs directory exists. - 100workflow-next
Use when: you want to advance the workflow state of the project to the next stage after satisfying all validations.