Ora Workflow

Planning (in plan mode)

1. Landscape scan: ora:Ariadne (always) + ora:Clio (if task involves externals) — understand what exists, not how to change it.
2. Classify ambiguity: vague request, multiple systems, unclear acceptance criteria → /brainstorm first. Clear and well-scoped → skip to 3.
3. Deep targeted exploration: Ariadne/Clio on the clarified scope.
4. Write plan informed by the analysis.

Execution (after plan mode)

5. Spawn ora:Hephaestus in worktrees (parallel for independent tasks). Research in this phase is rare — only when execution reveals something the plan could not have anticipated.

Do not Edit/Write in main after plan mode exits. All implementation runs through Hephaestus — dispatch a new wave for any change touching 2+ files or >10 lines. Exceptions: typo/comment fixes, removing an unused import, or a 1-line syntax error pointed out explicitly by Aletheia/Hephaestus output. Any code change that requires reading surrounding context first goes to Hephaestus.

Verification — do not skip