SpecJudge is presented as a local tool that reads repository instruction files such as CLAUDE.md and AGENTS.md to recommend the least expensive coding model likely to handle that repository, while flagging insufficient context. The supplied results establish that these files encode repository-specific guidance, can be nested with closest-file precedence, and are used across multiple coding agents, but evidence on their value conflicts: some testing reports benefits, while other studies report higher token use and little or negative quality improvement. The snippets do not independently document SpecJudge’s creator, implementation, benchmark results, or whether instruction files contain enough signal for reliable model routing, so its core claim remains unverified here.
SpecJudge combines Scott’s existing CLAUDE.md-as-repository-spec pattern with his task-aware, cost-tiered model-routing work, while adding a concrete repository-level routing and insufficient-context decision. Independent results could affect how he builds routing into coding-agent harnesses—especially given his warning that bloated instruction files can increase cost and reduce success—but the tool’s claims and creator remain unverified, limiting relevance for now.
ip:concept.claude-md-patterndev:concept.task-aware-model-routingip:concept.fat-agents-md-anti-patternip:concept.evaluation-driven-developmentradar:concept.model-routingradar:multi-model-orchestrator-worker-agentsradar:karpathy-claude-md-rulesradar:concept.agent-evaluation
queries asked of Scott's wikis
- repository-aware coding model routing
- cheap-model escalation for coding agents
- CLAUDE.md and AGENTS.md as machine-readable repository specifications
- nested instruction precedence in agent harnesses
- task quality measurement for coding-agent routing
- insufficient-context detection and routing confidence
2026-08-20T09:37:53Z
After repeated reviews, SpecJudge has attracted no independent use, inspectable benchmark, or external implementation, and there is no concrete confirming event expected. The artifact has faded without advancing the repository-driven routing hypothesis, so the episode can close pending genuinely new evidence.
2026-08-18T09:34:02Z
The extra comments add no inspectable independent use, implementation, or controlled quality-cost result, so SpecJudge remains a low-traction maintainer claim rather than evidence for repository-driven model routing.
2026-08-16T09:30:11Z
No new evidence has appeared beyond the maintainer’s repeated claims, and the minor engagement changes add no independent use, benchmark, or release verification. The case remains an unvalidated implementation awaiting external results.
2026-08-14T08:39:34Z
The latest maintainer post broadens SpecJudge’s claimed implementation to one-command spec-kit installation and repository-context-based model ranking, but it remains the same creator’s unverified line of evidence. Without independent use or controlled quality-and-cost results, the case still does not show that repository instructions can route coding tasks safely.
2026-08-14T08:22:26Z
evidence attached: reddit.post.1vo0d71 — The tool directly implements repository-instruction-based model selection, materially bearing on the open routing hypothesis.
2026-08-12T10:30:08Z
The refreshed discussion is mostly dismissive or generic model-choice commentary and adds neither independent use nor a controlled quality-cost result. SpecJudge remains an unvalidated single-maintainer routing artifact rather than evidence that repository instructions can safely select cheaper models.
2026-08-10T10:24:41Z
The new post adds a maintainer-reported Haiku-versus-Sonnet anecdote, but changing both the model and specification makes it incapable of validating SpecJudge’s routing. The case still awaits independent use or a controlled quality-and-cost benchmark.
2026-08-10T10:22:08Z
evidence attached: reddit.post.1vkglyc — The post provides direct usage context for SpecJudge's repository-instruction-driven model selection hypothesis.
2026-08-08T14:35:02Z
The additional activity adds no independent implementation or quality-cost evidence; the case remains a single-maintainer claim awaiting external use or benchmarks.
2026-08-08T14:29:32Z
grounded: converges/medium — SpecJudge combines Scott’s existing CLAUDE.md-as-repository-spec pattern with his task-aware, cost-tiered model-routing work, while adding a concrete repository
2026-08-08T14:23:50Z
case created — The MIT-licensed CLI is a concrete new routing artifact, but its quality and cost benefits currently rest only on the developer's low-engagement announcement.