orchestratelisted

# flow:orchestrate — End-to-end workflow runner Orchestrate is a thin sequencer. It does not reimplement any of the individual skills — it invokes them in order, with skip logic based on size and explicit user signals. ## Inputs 1. **Task goal** — what the user wants built, in their words. 2. **Type hint** (optional) — feature / fix / chore / refactor / docs. Inferred from the goal if not given. 3. **Explicit skips** (optional) — e.g., "skip research", "skip the code-review brief at the end". Honor without arguing. ## The sequence ``` 0. flow:kickoff [front door — framing AND setup in one step] └── writes brief.md (GOAL, acceptance criteria + verification, scope, hypothesis, working rules), sets category + size, optionally posts a Korean GitHub Issue └── then scaffolds: worktree, branch, .flow/tasks/, prepare.md (with size estimate) └── if oversized (GOAL with >3 independent parts / separable areas): splits into a parent + sub-issues. Then orchestrate runs the loop below on the FIRST sub-issue only; each remaining sub-issue is its own kickoff→…→deploy run later. (Fast lane: flow:quick is the alternate entry for a user-asserted trivial task — it classifies green/yellow/red and, on green, jumps straight to develop. See flow:quick.) 1. flow:research [skip if size = S, or user opted out] └── writes research.md 2. flow:plan [always] └── (sub-phase) multi-LLM brainstorm if size = L, or size = M with