Skip to content

Conversation

@Perlover
Copy link
Contributor

With Claude Opus 4.5, the previous wording caused two issues:

  1. Multiple task groups in single implementer - Claude often attempted to pass all task groups to a single implementer subagent, exhausting context

  2. No subagent at all - Sometimes Claude implemented task groups directly in the current conversation window without spawning any implementer

This fix adds:

  • CRITICAL instruction to spawn SEPARATE implementer for EACH task group
  • Execution strategy based on task group dependencies
  • Examples of parallel execution (independent groups)
  • Examples of sequential execution (dependent groups)

Each subagent now gets its own context window for focused implementation.

🤖 Generated with Claude Code

…group

With Claude Opus 4.5, the previous wording caused two issues:

1. Multiple task groups in single implementer - Claude often attempted to
   pass all task groups to a single implementer subagent, exhausting context

2. No subagent at all - Sometimes Claude implemented task groups directly
   in the current conversation window without spawning any implementer

This fix adds:
- CRITICAL instruction to spawn SEPARATE implementer for EACH task group
- Execution strategy based on task group dependencies
- Examples of parallel execution (independent groups)
- Examples of sequential execution (dependent groups)

Each subagent now gets its own context window for focused implementation.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@Perlover Perlover force-pushed the fix/implement-tasks-separate-subagents branch from f53df53 to 4eee835 Compare December 18, 2025 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant