fest-standalone-workflows

# 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 workflo...