Skip to content

examples.md

Latest commit

 

History

History
56 lines (43 loc) · 2.41 KB

examples.md

File metadata and controls

56 lines (43 loc) · 2.41 KB
Raw

Routing examples

Use these as precedents, not fixed rules. Balance current quota before applying the provider preference.

Complex feature planning

  • Task: Design and plan a cross-cutting feature whose API and boundaries remain ambiguous.
  • Pattern: plan-build-verify
  • Host: Fable High in Claude or Sol High in Codex; escalate only if routing or integration proves insufficient.
  • Planning worker: Opus High or Sol High drafts options, boundaries, and risks; the host freezes the spec.
  • Implementation worker: choose per coherent unit after the spec is frozen.
  • Adversarial: on.
  • Rationale: delegate architecture analysis without delegating the host's routing decision or final accountability.

Frozen backend implementation

  • Task: Implement a clear backend plan with exact tests.
  • Pattern: plan-build-verify
  • Worker: Sol Medium or Sonnet Medium/High, chosen primarily by quota.
  • Adversarial: on; use the stronger opposite provider.
  • Rationale: routine code volume belongs in a worker, not the host.

Frontend feature

  • Task: Build a responsive user-facing flow with visual and interaction requirements.
  • Pattern: frontend
  • Worker: prefer Sonnet or Opus when quota permits.
  • Adversarial: on; use Sol High and include rendered evidence.
  • Rationale: Anthropic is the default task-fit preference for frontend, while GPT supplies an independent check.

Quick repository map

  • Task: Locate the implementation of a behavior and summarize its control flow without editing.
  • Pattern: explore
  • Worker: Luna xhigh; escalate to Sol High when synthesis is inadequate or the decision is high risk.
  • Adversarial: off unless the result drives a consequential architecture or security decision.
  • Rationale: isolate context-heavy reading from the host.

Tiny organization action

  • Task: Move files, organize folders, or perform a small clerical computer action.
  • Pattern: none; dispatch as one lightweight unit unless the action is truly atomic and dispatch overhead would exceed execution.
  • Worker: Haiku in Claude or Luna low/medium in Codex.
  • Adversarial: off.
  • Rationale: lightweight actions still default downward; direct host work requires the atomic-work exception.

Example entry template

## <short task class>
- Task: <concrete request>
- Pattern: <pattern name or none>
- Worker: <model/effort and provider preference>
- Adversarial: <on or off; verifier if on>
- Rationale: <why this route is reusable>