flow-orchestratorlisted

# Flow Orchestrator ## Purpose Flow Orchestrator is the Task Manager-aware implementation orchestrator. It wraps the existing gdskills pipeline with `keryx flow` state. Use this skill instead of `job-orchestrator` when the user wants a managed story/issue lifecycle with frozen acceptance criteria, task state, an explicit completion choice, Code Health, and a durable flow package in `.metaproject/flows/`. Do not modify `job-orchestrator` or `task-implementer` behavior. They remain usable without Task Manager. This skill coordinates them through flow state. ## Hard Preconditions 1. Read `.metaproject/index.md` and `.metaproject/metaproject.json`. 2. Confirm Task Manager is enabled: - `.metaproject/metaproject.json` must contain `modules.tasks.enabled: true`; - `.metaproject/skills/flow/SKILL.md` should exist. 3. If Task Manager is not enabled, stop and tell the user to run: ```bash keryx update ``` or initialize with the Task Manager module enabled. Do not emulate flow state by hand. ## Source Of Truth Flow state lives in `.metaproject/flows/<flow-id>/`. CLI-owned files: - `flow.json` - never edit by hand. - status transitions - only through `keryx flow ...`. - task status - only through `keryx flow task done ...`. - frozen acceptance criteria changes - only through `keryx flow ac update <id> --reason "<why>"`. Agent-editable files: - `description.md` - `context.md` - `plan.md` - `tasks.md` for task definitions only - `journal.md` ## Lifecycle ```mermaid