Detailed Analysis
A Reddit user posting in r/Anthropic describes a workflow built around a tool called GSD (Get Shit Done) that uses Claude as its underlying model, and articulates a specific set of requirements for a more capable multi-model orchestration layer. The user's core frustration is not with Claude's quality — which they describe as the best model to work with — but with the economic and operational constraints of Claude's pricing and the token limits imposed within a five-hour weekly session window. Their ask is for a harness that can decompose projects into milestones and phases, allow deliberate context resets between phases, and route specific task types to different language models based on cost-efficiency and capability fit.
The requirements outlined reflect a sophisticated understanding of how production AI workflows actually function under real-world constraints. The user's phase-based context clearing strategy — already implemented in GSD — is a practically important technique: by resetting context between discrete project phases, the system prevents token accumulation from degrading model performance and keeps API costs manageable. This is not a casual optimization but a workflow discipline that mirrors how professional engineering teams think about state management in long-running processes. The multi-model routing concept they describe — Anthropic for research, GPT for coding, cheaper models for documentation — mirrors emerging enterprise patterns where heterogeneous model fleets are composed based on task complexity and cost tolerance rather than defaulting to a single flagship model.
The post inadvertently surfaces a notable gap in the current AI tooling landscape. Despite the rapid proliferation of agent frameworks — LangChain, LangGraph, AutoGen, CrewAI, and others — the user reports difficulty finding any tool that satisfies this particular combination of features: milestone-based project decomposition, explicit context lifecycle management, and per-task model routing. This suggests that most open-source orchestration frameworks still optimize for single-model pipelines or treat multi-model routing as a secondary concern, rather than building it into the core project management abstraction.
The broader trend this post reflects is the maturation of AI power users beyond single-session prompting into structured, multi-phase project execution. As context windows have grown, the assumption has been that larger context eliminates the need for state management — but practitioners like this user are discovering that deliberate context scoping remains important for cost control and model reliability even with large windows. The demand for model-agnostic orchestration layers that treat different LLMs as interchangeable specialists for different subtasks represents a meaningful direction for the next generation of AI development tooling, and the fact that no obvious off-the-shelf solution exists yet points to a genuine product opportunity in the space.
Read original article →