Repository navigation
fix(skills): have muster and the steward cut each bead to one outcome - #105
Merged
Merged
Conversation
GraemeF
force-pushed
the
worktree-yard-jpvb
branch
from
October 26, 2026 14:33
951ab30 to
3f892f7
Compare
GraemeF
marked this pull request as ready for review
October 26, 2026 14:35
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
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.
The bar said one bead is one worker is one context, so beads were cut to what one agent can finish and came out with titles joining two outcomes. The bar, muster's size audit and the steward's sizing section now cut each bead to one outcome, still splitting a bead too big for one context, and leave how many beads a worker takes to the steward when it starts the seat.