Problem
None of the existing orchestration modes serves lightweight coding tasks well:
vibe is fast (no architecture/planning) but lenient — high thresholds mean most findings pass without being fixed, and 1 review round means no fix-and-re-review cycle is possible.
- Default maintains quality but adds architecture and planning phases that are overkill for minor tasks, plus 3 review rounds.
strict is the most thorough but also the most expensive.
There's a gap for work where we want speed (skip arch/plan) but still care about code quality (low thresholds, at least one fix cycle).
Proposal
Create a new lightweight mode, --mode=lite, that fills this gap:
| Setting |
vibe |
lite |
(default) |
strict |
| architecture |
absent |
absent |
optional |
required |
| planning |
absent |
absent |
optional |
required |
| approval-threshold |
high |
low |
low |
low |
| budget-threshold |
high |
low |
low |
low |
| holistic_reviewer* |
sonnet |
sonnet |
opus |
opus |
| max-review-rounds |
1 |
2 |
3 |
4 |
Positioning: vibe (fast + lenient) → lite (fast + quality) → default (balanced) → strict (thorough).
Settings rationale
- architecture/planning: absent — Same as vibe. Eliminates the heaviest per-task overhead for minor tasks.
- approval-threshold/budget-threshold: low — Same as default/strict. All findings are in scope for fixing. This is the key quality difference from
vibe (which uses high, letting most findings pass).
- holistic_reviewer: sonnet — Aspect reviewers already do focused analysis; the holistic pass is a sanity check. Sonnet is sufficient and saves cost vs opus.
- max-review-rounds: 2 — The minimum for a meaningful fix cycle. With
vibe's 1 round, findings are reported but can't be fixed (no remaining rounds). With 2 rounds, the initial review + 1 fix iteration is possible.
Scope
Two files need changes:
packages/agents/content/skills/orchestrate-dev/SKILL.md — Add lite to the --mode enum, mode presets table, and pipeline-per-mode section.
packages/agents/content/skills/orchestrate/SKILL.md — Update the wrapper skills reference to include lite in the mode list (documentation only; the engine is mode-agnostic).
Acceptance criteria
Problem
None of the existing orchestration modes serves lightweight coding tasks well:
vibeis fast (no architecture/planning) but lenient — high thresholds mean most findings pass without being fixed, and 1 review round means no fix-and-re-review cycle is possible.strictis the most thorough but also the most expensive.There's a gap for work where we want speed (skip arch/plan) but still care about code quality (low thresholds, at least one fix cycle).
Proposal
Create a new lightweight mode,
--mode=lite, that fills this gap:vibelitestrictPositioning:
vibe(fast + lenient) →lite(fast + quality) → default (balanced) →strict(thorough).Settings rationale
vibe(which useshigh, letting most findings pass).vibe's 1 round, findings are reported but can't be fixed (no remaining rounds). With 2 rounds, the initial review + 1 fix iteration is possible.Scope
Two files need changes:
packages/agents/content/skills/orchestrate-dev/SKILL.md— Addliteto the--modeenum, mode presets table, and pipeline-per-mode section.packages/agents/content/skills/orchestrate/SKILL.md— Update the wrapper skills reference to includelitein the mode list (documentation only; the engine is mode-agnostic).Acceptance criteria
--mode=liteis accepted byorchestrate-devlitecolumn betweenvibeand(default), with values matching the table abovelitemode skips architecture and planning (identical tovibe's pipeline)litealongsidevibeandstrictpnpm run buildsucceedspnpm run checkpasses