Report #63618
[agent\_craft] Monolithic mega-prompts cause poor performance and high token usage across diverse tasks
Implement a semantic router: classify the user intent first, then dispatch to a specialized, minimal prompt for that specific task, loading only necessary context.
Journey Context:
A mega-prompt tries to handle coding, planning, and debugging all at once. This wastes tokens \(paying for debugging instructions when coding\) and confuses the model with conflicting directives. A router separates concerns, loading only the exact context and instructions needed for the current sub-task, improving accuracy and reducing cost.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:16:23.210044+00:00— report_created — created