fix: clarify separate implementer subagent per taskgroup #292
+24
−7
Conversation
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
…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]>
f53df53 to
4eee835
Compare
dchuk
added a commit
to dchuk/agent-os
that referenced
this pull request
Jan 12, 2026
…pstream PR buildermethods#294 Adapt improvements from buildermethods/agent-os PR buildermethods#294 to work with our JSON-based workflow system. These changes prevent false task completion and improve refactoring task handling. Changes to implement-tasks.md: - Add CLAUDE.md reading instruction for project-specific rules - Add skills discovery via <available_skills> section - Add 6 critical task completion rules: - Rule 1: Tasks complete only when actually executed - Rule 2: Handle missing prerequisites (start services, don't install deps) - Rule 3: Task groups require all tasks complete - Rule 4: TDD phases require actual test execution - Rule 5: Verification tasks require evidence - Rule 6: Incomplete tasks must stay incomplete Changes to create-tasks-list.md: - Add Step 1.5: Spec completeness verification for refactoring tasks - Run grep searches to find all affected files before creating tasks - Document gaps between spec and actual codebase impact Changes to research-spec.md: - Add Question 8 for impact analysis during requirements gathering - Add Impact Analysis section to requirements.md template - Capture affected areas for refactoring tasks Changes to write-spec.md: - Add Step 2.5: Comprehensive impact analysis for refactoring - Add "Files Requiring Modification" section to spec.md template - Check for duplicate definitions and related mappings Note: PRs buildermethods#301 (Chrome alias) and buildermethods#292 (separate subagents) were already merged. PR buildermethods#293 (init-spec clarity) not applicable due to JSON workflow rewrite. Co-Authored-By: Claude Opus 4.5 <[email protected]>
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.
With Claude Opus 4.5, the previous wording caused two issues:
Multiple task groups in single implementer - Claude often attempted to pass all task groups to a single implementer subagent, exhausting context
No subagent at all - Sometimes Claude implemented task groups directly in the current conversation window without spawning any implementer
This fix adds:
Each subagent now gets its own context window for focused implementation.
🤖 Generated with Claude Code