model-routing

Reference: Model Routing Recommendations

Operator hints to choose an appropriate model style per prompt. Keep these as guidance; do not encode as front matter.

author-specification

• Goal: Clarify requirements; produce a deterministic spec using repo analysis
• Model: Reasoning-capable generalist
• Temperature: 0.2–0.4
• Notes: Allow tools to scan repo; prefer structured outputs

derive-implementation-plan

• Goal: Convert spec into traceable plan
• Model: Structured reasoning with planning strength
• Temperature: 0.2–0.3
• Notes: Emphasize table/ID consistency; validate cross-references

decompose-feature-work

• Goal: Break down feature into WIs/tests/docs
• Model: Balanced coder-planner
• Temperature: 0.2–0.4
• Notes: Deterministic formatting; enforce ID usage

implement-next-work-item

• Goal: Apply minimal, correct code changes with tests
• Model: Strong code generator with tool use
• Temperature: 0.1–0.2
• Notes: Prefer small diffs; run builds/tests after edits

author-adr

• Goal: Record decision and rationale
• Model: Analytical, explanation-leaning
• Temperature: 0.2–0.3
• Notes: Require alternatives and impacts list

propagate-adr

• Goal: Make consistent edits across artifacts
• Model: Structured editor
• Temperature: 0.1–0.2
• Notes: Prioritize consistency and validation rules

author-refactor-plan

• Goal: Safely plan refactors
• Model: Analytical with risk assessment
• Temperature: 0.2–0.3
• Notes: Include risks, tests, rollback strategy