Skip to content

Clarify self-contained plan slices#9

Merged
The-Rabak merged 1 commit into
feat/workflow-contract-overhaulfrom
feat/plan-contained-subphases
Apr 27, 2026
Merged

Clarify self-contained plan slices#9
The-Rabak merged 1 commit into
feat/workflow-contract-overhaulfrom
feat/plan-contained-subphases

Conversation

@The-Rabak
Copy link
Copy Markdown
Owner

Summary

Tighten /workflows-plan so each subphase/task is authored as a self-contained execution unit.

What changed

  • add explicit guidance that each task slice should stand on its own once dependencies are satisfied
  • require task scope/boundary language in addition to files, dependencies, success criteria, and test command
  • clarify that /workflows:work should be able to execute a task without reconstructing intent from neighboring phases
  • extend the plan contract test so this rule stays enforced across generated outputs

Tighten the workflows-plan contract so each subphase/task is described as a
self-contained execution unit instead of an implied continuation of adjacent
phases.

- require each task slice to carry explicit scope and containment boundaries
- stress that executors should have the files, success criteria, and
  verification command needed once dependencies are satisfied
- update the execution-readiness checklist to reject plans with missing task
  boundaries
- cover the new planning language with a contract test so the rule stays
  enforced in generated outputs

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@The-Rabak The-Rabak merged commit 7aac2a3 into feat/workflow-contract-overhaul Apr 27, 2026
1 check failed
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