← ClaudeAtlas

agentic-driving-weaker-modelslisted

Operating manual for getting strong-model-quality results out of cheaper/smaller agent sessions, based on observed failure modes from validation dry runs and two projects' review history. Use when: choosing which model tier runs a task; composing a brief for a cheaper session; a session keeps making a characteristic mistake (trusting docs without verifying, fixing the symptom not the contract, skipping gates under constraint); deciding whether to escalate to a stronger model or the human; a cheaper agent wants to self-check its own known weak spots before delivering. Covers the gap taxonomy, the mitigation matrix, the task→tier routing table, brief-composition checklists, and escalation triggers. NOT for reviewer-brief mechanics (agentic-review-orchestration) or raw cost math (agentic-session-economics).
gidde032/agentic-workflow · ★ 0 · AI & Automation · score 63
Install: claude install-skill gidde032/agentic-workflow
# Driving weaker models — the playbook **The central claim:** a weaker model inside a strong verification harness approximates a stronger system. Cheaper-tier dry runs passed inside the harness — skills, gates, review, paired tests — while in the same period the strongest available model authored three plans that cold review raised 32 findings against, 4 of them CRITICAL. The harness is not a patch for weak models; it is the system, and every tier needs it. Tier buys fewer errors, not zero. What changes by tier is how much structure the brief must carry and where the human checkpoint goes. Observations, evidence base, and provenance: `examples.md`. --- ## 1. The gap taxonomy — where cheaper sessions actually differ Observed, not assumed. Each gap: the evidence, then what it predicts. **G1 — Trusted docs are treated as ground truth; the verify instinct doesn't fire.** An agent repeated a stale skill claim verbatim rather than spending one `git ls-files` to check it, while otherwise executing doctrine perfectly. Predicts: any error in your skills, briefs, or specs propagates straight into output. Corollary: skill and spec correctness is load-bearing — review and dry-run-validate them. Seven skill patches came out of four dry runs. **G2 — Fluent, unresolved self-contradiction in analysis prose.** A debugging run delivered a correct fix wrapped in a diagnosis that claimed an impossible thing, noticed the tension mid-paragraph, and moved on without resolving it. Predicts: