Skip to content

feat(prompts): aggressive parallelization for COMPLEX issue workflows#1018

Merged
acreeger merged 1 commit into
mainfrom
feat/aggressive-complex-parallelization
May 21, 2026
Merged

feat(prompts): aggressive parallelization for COMPLEX issue workflows#1018
acreeger merged 1 commit into
mainfrom
feat/aggressive-complex-parallelization

Conversation

@acreeger
Copy link
Copy Markdown
Collaborator

Summary

  • Update planner agent to default ALL steps to parallel execution, only sequentializing when files conflict — adopts the architect agent's "contracts over dependencies" philosophy
  • Add "Parallel Wave Awareness" section to implementer agent so it knows compile errors from missing parallel-step modules are expected, not failures
  • Add post-wave validation checkpoint in issue-prompt for non-swarm COMPLEX execution — verifies integrated result compiles after each parallel wave

Test plan

  • Run a COMPLEX issue workflow and verify the planner produces more aggressively parallel execution plans
  • Verify implementer agents handle expected compile errors from parallel steps gracefully
  • Verify post-wave validation catches real integration errors after parallel steps complete

Update planner agent to produce more aggressively parallel execution
plans using contract-based parallelism — default all steps to parallel,
only sequentialize when files conflict. Add implementer awareness of
parallel wave execution so compile errors from missing parallel-step
modules are expected, not failures. Add post-wave validation checkpoint
in issue-prompt for non-swarm COMPLEX execution.
@acreeger acreeger merged commit 2569d8f into main May 21, 2026
4 checks passed
@acreeger acreeger deleted the feat/aggressive-complex-parallelization branch May 21, 2026 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant