flowlisted

Orchestrates the full supermodo development pipeline end-to-end for one task, running each stage in its own subagent so the main context stays small. Eight stages: librarian task intake (grilled), work implementation, optional hunt bug audit, tdd fixes for any bugs found, a mandatory tests gate (suite green + coverage target), refactor, a mandatory post-refactor verify gate, a final librarian docs pass, and commit. Supports entering at a later stage (--from work|hunt|tests|refactor|librarian|commit) and three job sources: an existing docs/work triad, a backlog entry, or a completely new task — with a context-aware "next job" suggestion when none is named. Use when the user wants to run the whole pipeline, "take this task from spec to commit", orchestrate a feature end-to-end, run the full flow (or the flow from a given stage), or drive a task through the complete dev-to-commit process — anything that means coordinating grill → work → hunt → tdd → tests → refactor → librarian → commit rather than a single stag
supermodo/skills · ★ 1 · Testing & QA · score 77

Install: claude install-skill supermodo/skills

# flow — pipeline orchestrator > **Requires:** the sibling `protocols` skill (shared protocol masters) and a valid `skills.config.json` (create with the `config` skill). Missing either → halt with that exact pointer; never guess. A THIN orchestrator. It runs stages, validates their reports, routes questions, and keeps run state — it never implements, tests, or edits docs itself. All real work happens in per-stage subagents; handoff travels through report files on disk, not through this context (see `../protocols/references/handoff.md`). > **Cross-tool note (Claude Code ↔ Codex).** Written in Claude Code idioms. > Subagent spawning and **persistent continuation** (`SendMessage` to a live > agent) are the Claude Code path. Under Codex, spawning/continuation differ: the > declared fallback for `needs-input` is **rerun-with-answers** (re-invoke the > stage with answers injected), and question transport degrades to chat. Declare > the fallback in state and use it. ## Invocation — job source and entry stage `flow [--from <stage>] [--job <source>]` — both optional; plain `flow` = full pipeline, job chosen interactively. **Job source** (`--job`) — where the task comes from: - `work:<triad-path>` — an existing triad in `docs/work/`, named by its identity path per the docs convention (`<task-slug>` flat, or `<program>/NN-<slug>` for a program initiative). Stage 1 skips creation: librarian validates it against the convention and grills only the gaps found (its existing "n