Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
"name": "workflow-orchestrator",
"source": "./",
"description": "Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code",
"version": "2.0.1",
"version": "2.0.2",
"author": {
"name": "Nadav Barkai"
},
Expand Down
2 changes: 1 addition & 1 deletion .claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "workflow-orchestrator",
"version": "2.0.1",
"version": "2.0.2",
"description": "Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code",
"author": {
"name": "Nadav Barkai"
Expand Down
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,12 @@

All notable changes to this project will be documented in this file.

## [2.0.2] - 2026-04-12

### Added

- **Skip plan mode for fully-specified sequential tasks.** New routing step (Step 3: Fully-Specified Task Detection) in `commands/delegate.md`. When the user provides explicit ordered steps with no ambiguities or design decisions, the orchestrator routes to direct sequential execution instead of entering plan mode unnecessarily. Detects numbered steps, imperative chains, and explicit signals like "just do it" or "no plan needed".

## [2.0.1] - 2026-04-12

### Fixed
Expand Down
20 changes: 17 additions & 3 deletions commands/delegate.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Multi-step workflow orchestration for Claude Code. Main agent enters plan mode (

## ROUTING (CHECK FIRST - MANDATORY)

**Three-step routing check. MUST follow this order:**
**Four-step routing check. MUST follow this order:**

### Step 1: Write Detection

Expand All @@ -36,12 +36,26 @@ Multi-step workflow orchestration for Claude Code. Main agent enters plan mode (

**Breadth keywords:** review, analyze, summarize, scan + quantifiers like "all", "each", "files in", or explicit counts

### Step 3: Route Decision
### Step 3: Fully-Specified Task Detection

**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.
Comment on lines +41 to +50

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

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


### Step 4: Route Decision

| Pattern | Route | Example |
|---------|-------|---------|
| Breadth + Write (same op x many items, with output) | **DIRECT EXECUTION** (skip plan mode) | "review 16 files, create reports" |
| Multi-phase workflow (create -> test -> deploy) | plan mode (EnterPlanMode) | "create calculator with tests and verify" |
| Fully-specified sequential task (all steps explicit) | **DIRECT SEQUENTIAL EXECUTION** (skip plan mode) | "bump version, commit, push, merge, tag, release" |
| Multi-phase workflow (needs design/decomposition) | plan mode (EnterPlanMode) | "create calculator with tests and verify" |
| Read-only breadth (no write indicators) | Spawn parallel Explore agents or codebase-context-analyzer | "explore code in X", "summarize files in X" |
| Single simple task | general-purpose agent | "fix this bug" |

Expand Down
Loading