workflow-start

# Workflow Start Primary entry point for `spec-superflow`. Jobs: inspect change context, check for updates, confirm DP-0, determine state, route to correct skill, block invalid transitions. ## Use This Skill When Only invoke when spec-superflow context is present: `.spec-superflow.yaml` exists, artifacts like `proposal.md`/`specs/`/`design.md`/`tasks.md`/`execution-contract.md` are present, or user explicitly invokes spec-superflow by name. When in doubt, check for `.spec-superflow.yaml` first. Do NOT invoke for: general coding tasks outside spec-superflow changes, casual questions, unrelated work. ## States `exploring` → `specifying` → `bridging` → `approved-for-build` → `executing` → `closing`, with `debugging` side-path from `executing`, and `abandoned` as terminal. If a transition is ambiguous, run `ssf runtime asset read docs/state-machine.md`. ## Terminal-State Short Circuit Before update checks or recovery overlays, inspect the persisted state. If it is `closing`, stop immediately: `closing` is a successful terminal state and the next skill is `none`. Report the terminal state and its persisted evidence. Do not run `handoff list`, `checkpoint list`, the execution-control recovery scan, or `release-archivist`; do not resume, hand off, or route any more work. ## Initialization 1. **Update check**: Run `ssf runtime check-update`. Exit 0 → continue. Exit 1 → non-blocking upgrade reminder. Exit 2 → skip. 2. **Inspect change folder**: Check for `proposal.md`, `spec...