Skip to content

feat(writing-plans): add parallel suitability check to plan handoff#970

Open
leonsong09 wants to merge 1 commit intoobra:mainfrom
leonsong09:feat/writing-plans-parallel-suitability
Open

feat(writing-plans): add parallel suitability check to plan handoff#970
leonsong09 wants to merge 1 commit intoobra:mainfrom
leonsong09:feat/writing-plans-parallel-suitability

Conversation

@leonsong09
Copy link
Copy Markdown

Summary

This is a narrow writing-plans improvement aimed at making execution routing more explicit without making Superpowers parallel-first.

It adds:

  • per-task execution metadata in the plan template:
    • Depends on
    • Write Scope
    • Verify
    • Potential Conflicts
  • a short Parallel Suitability Check section before execution handoff
  • a handoff pattern that gives a recommended execution mode (Iterative or Parallel-safe) with reasoning
  • plan-reviewer guidance to check whether the plan is explicit enough to choose the right execution path
  • small prompt fixture updates so the explicit-skill-request prompts reflect the new handoff wording

Why

Today writing-plans decomposes work into tasks, but the handoff does not make it easy to tell:

  • which tasks are truly independent
  • which tasks share write scope or contracts
  • whether the safest next step is iterative execution or a parallel-safe path

This PR keeps the current correctness-first bias, but makes plans clearer and more actionable when some tasks are independent.

Non-goals

This PR does not:

  • make Superpowers parallel-by-default
  • introduce a new orchestration skill
  • replace heavier multi-agent flows like agent-teams / assemble
  • change the recommendation that iterative execution is safest when tasks are coupled

Related discussion

Verification

Ran targeted verification directly related to these documentation/prompt changes:

  • git diff --check
  • grep/rg checks for the new handoff markers (Execution Recommendation, Parallel Suitability Check, Execution Readiness)
  • confirmed changed file set stayed limited to the intended 4 files

I did not claim broader build/test coverage because this change is limited to skill/prompt markdown and there is no direct unit/build target for it in this repo.

@obra obra added enhancement New feature or request plans Planning workflow (writing-plans, executing-plans) pr-template-rules-ignored PR filed after template was added but didn't use it labels Mar 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request plans Planning workflow (writing-plans, executing-plans) pr-template-rules-ignored PR filed after template was added but didn't use it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants