orch-ui

Invoke /orch-ui with a task description, confirm the suggested cycle-type (e.g. feature-cycle), and it runs analyze, plan, impl, validate, cleanup, commit, and retro in order. Each step executes in its own isolated subagent and hands off through files in the skill-output directory.

feature-cycle runs the full analyze, plan, validate, cleanup, commit, retro loop with opus-tier planning and validation gates. simple-task runs only impl, cleanup, and commit on sonnet and haiku, intended for small already-scoped changes like copy fixes or one-file edits.

A failed step with stop_on_fail halts the cycle unless it declares bounded remediation. With remediation configured, the orchestrator spawns the remediation skill against the failing artifact and re-runs the gate, up to the configured round cap, before halting.

Yes. Steps with scope set to repo resolve the skill from the triggering repo's .agent/skills or .claude/skills directory. If the repo does not provide that skill, the step is skipped automatically rather than failing.

BLOCKED means an isolated subagent raised decision memos instead of guessing, since subagents cannot ask questions directly. The orchestrator presents each open memo to you, records your answers, then re-runs the same step and continues the cycle.

Avoid simple-task when the change spans multiple files or domains, the approach is undecided, or the result needs a behavioral validation gate beyond lint and type checks. Those cases need feature-cycle's analyze, plan, and validate steps.