These examples show what codex-flow is meant to unlock for Codex users: maintainer workflows that are too broad for one linear agent turn.
All workflow examples are import-free and use plain JSON Schema, so you can copy them into any project without installing repo-local helpers.
After installing the bundled Codex skill:
codex-flow try
codex-flow install-codex
codex-flow doctorRestart Codex, open any project, and say:
use a dynamic workflow to investigate this bug in parallel
Codex should generate a temporary .codex-flow/generated/*.workflow.ts, run it, and summarize the journaled results.
Parallel bug investigation over several hypotheses or repository areas, then one synthesized action plan.
codex-flow run examples/bug-investigation.workflow.ts --backend codex-sdkFan out PR review into correctness, regression risk, tests/docs, and API/sandbox passes, then merge the verdict.
codex-flow run examples/pr-review.workflow.ts --backend codex-sdkFan out issue classification and priority calls, then merge them into one maintainer action.
codex-flow run examples/issue-triage.workflow.ts --backend codex-sdkRun read-only release checks over package metadata, README, CLI examples, and release docs.
codex-flow run examples/release-smoke.workflow.ts --backend codex-sdkA minimal real Codex structured-output call.
codex-flow run examples/hello.workflow.ts --backend codex-sdkA tiny fake-backend workflow for local smoke testing without network or Codex login.
codex-flow run examples/pong.workflow.ts --backend fakeA larger workflow shape for maintainer-style investigation: split a problem, run parallel branches, collect structured findings, and resume from the journal if interrupted.
codex-flow run examples/triage.workflow.ts --backend codex-sdk