Feat/workflow contract overhaul#10
Merged
Merged
Conversation
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>
Clarify self-contained plan slices
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
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.
No description provided.