feat: skip plan mode for fully-specified sequential tasks#44
Merged
Conversation
Add Step 3 (Fully-Specified Task Detection) to the routing table in delegate.md. When the user provides explicit ordered steps with no ambiguities or design decisions, the orchestrator now routes to direct sequential execution instead of entering plan mode unnecessarily. Detection indicators: - Numbered/ordered steps in the request - Imperative sequential chains with concrete steps - Explicit signals: "just do it", "no plan needed" - All steps map trivially to tool calls - Zero ambiguity markers Closes #43 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Review Summary by QodoAdd fully-specified task detection to skip plan mode
WalkthroughsDescription• Adds Step 3 (Fully-Specified Task Detection) to routing table • Detects explicit ordered steps to skip plan mode • Enables direct sequential execution for trivial workflows • Reduces unnecessary planning for concrete multi-step tasks Diagramflowchart LR
A["User Request"] --> B["Step 1: Write Detection"]
B --> C["Step 2: Breadth Detection"]
C --> D["Step 3: Fully-Specified Task Detection"]
D --> E{Task Type}
E -->|Explicit Ordered Steps| F["Direct Sequential Execution"]
E -->|Multi-phase Workflow| G["Plan Mode"]
E -->|Read-only Breadth| H["Parallel Explore Agents"]
E -->|Single Task| I["General-purpose Agent"]
File Changes1. commands/delegate.md
|
Contributor
Code Review by Qodo
|
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
Comment on lines
+41
to
+50
| **Pattern:** The user provided explicit, ordered steps with no ambiguities or design decisions needed. Every step is directly actionable without decomposition. | ||
|
|
||
| **Indicators (ANY of these):** | ||
| - Numbered or ordered steps in the request ("1. do X, 2. do Y, 3. do Z") | ||
| - Imperative sequential chain ("do X, then Y, then Z" where each step is concrete) | ||
| - Explicit skip-planning signals: "just do it", "no plan needed", "skip planning", "don't plan" | ||
| - All steps map trivially to tool calls (edit file, run command, commit, push, merge, tag, release) | ||
| - Zero ambiguity: no "should we", "which approach", "evaluate options", "design" | ||
|
|
||
| **If fully-specified -> DIRECT SEQUENTIAL EXECUTION** (skip plan mode). Spawn one agent per step or batch related steps into a single agent. No `EnterPlanMode`, no `TaskCreate` during planning. |
Contributor
There was a problem hiding this comment.
1. Overbroad skip-plan criteria 🐞 Bug ≡ Correctness
Step 3 claims fully-specified tasks have “no ambiguities”, but the routing trigger is “ANY of these” indicators (including just “numbered steps”), so ambiguous numbered multi-step requests can be incorrectly routed to DIRECT SEQUENTIAL EXECUTION and skip required planning/decomposition.
Agent Prompt
## Issue description
The new “Fully-Specified Task Detection” uses an overly permissive OR condition ("ANY of these"), which can route ambiguous multi-step tasks to direct sequential execution.
## Issue Context
The text says the pattern requires “no ambiguities or design decisions”, but the detection criteria does not enforce that as a gate.
## Fix Focus Areas
- commands/delegate.md[39-51]
- commands/delegate.md[54-60]
## Suggested change
- Replace “Indicators (ANY of these)” with an explicit gated rule such as:
- (skip-planning phrase present) OR (ordered steps AND each step is concrete)
- AND no ambiguity markers are present ("should we", "which approach", "evaluate", "design", etc.)
- AND steps map trivially to tool calls
- Add an explicit fallback: if any ambiguity marker exists, route to plan mode.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
commands/delegate.mdProblem
The orchestrator entered plan mode for every multi-step task, even trivially specified ones like "bump version, commit, push, merge, tag, release." The user had to reject the plan and say "just do it." (#43)
Detection Indicators
Test plan
/workflow-orchestrator:delegate bump version to X, commit, push, merge— should skip plan mode/workflow-orchestrator:delegate create a calculator with tests and verify— should still enter plan mode (needs decomposition)/workflow-orchestrator:delegate just do it: edit file X, commit, push— should detect "just do it" signal and skip plan modeCloses #43
🤖 Generated with Claude Code