What's New
Intelligent Planning Flow
The orchestrator now acts as a context broker for Prometheus, eliminating unnecessary user questions about the codebase.
Features
-
Broad Request Detection: Automatically detects vague/unbounded requests that need planning
- Triggers on scope-less verbs: "improve", "enhance", "fix", "refactor" without specific targets
- Activates when no specific file or function is mentioned
- Engages when request touches multiple unrelated areas (3+ components)
-
Context Brokering Protocol: Before invoking Prometheus for planning:
- Orchestrator invokes
exploreagent to gather codebase context - Optionally invokes
oraclefor architectural guidance - Passes pre-gathered context to Prometheus
- Prometheus asks ONLY user-preference questions (not codebase questions)
- Orchestrator invokes
-
Question Classification: Prometheus now classifies questions before asking:
- Codebase facts → Uses provided context (doesn't ask user)
- User preferences → Asks user
- Requirements/scope → Asks user
Impact
Users no longer need to answer questions like "Where is X implemented?" or "What patterns exist?" - the orchestrator gathers this information automatically before planning begins.
Files Changed
docs/CLAUDE.md- Added broad request detection heuristic and context brokering protocolagents/prometheus.md- Added context-aware interview modesrc/agents/prometheus.ts- TypeScript agent definition updatedsrc/agents/definitions.ts- Legacy definitions updated
Full Changelog: v2.3.0...v2.4.0