Repository navigation
fix: smaller waves on refused spawns; enforce Stage 1 gate in hook (v3.2.1) - #8
Merged
Merged
Conversation
Why: in a trial run a machine-local cap of three concurrent subagents refused Stage 1's fourth writer, and the lead stopped the unattended run to ask whether to wait or write the files itself. Caps, rate limits, usage limits and hooks can all refuse a spawn. The lead now runs the remaining teammates in smaller waves, down to one at a time, keeps their separate contexts, and writes files itself only as a recorded last resort. The rule is in the pipeline agent and in the project CLAUDE.md template so stages invoked directly follow it too; conformance checks both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A trial on the sample plan produced a BRD that was 60% assumptions. The pipeline agent stops there, but stages invoked directly did not: Stage 2 ran for 51 minutes and Stage 2B could only return FAIL. The hook now blocks prd and validate-specs until the operator marks the assumptions reviewed, matching the bold marker the review log actually writes. trial-run.sh gains ACCEPT_ASSUMPTIONS=1 for fixture plans. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
masterleopold
changed the title
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.
A trial run hit a machine-local cap of three concurrent subagents during Stage 1; the lead stopped the unattended pipeline to ask the operator. This adds a spawn-refusal rule (run the rest in smaller waves, keep separate contexts, write files yourself only as a recorded last resort) to the pipeline agent's Execution Model and to the generated project's CLAUDE.md, plus a conformance check.
Held until the running trials finish, since they load the plugin from the main working tree.
Also: Stage 1 assumption gate in the hook
The sample-plan trial produced a BRD that was 60% assumptions. Stage 2 ran for 51 minutes and Stage 2B could only return FAIL, because stages invoked directly skipped the pipeline agent's Stage 1 stop. The hook now blocks
prdandvalidate-specsuntil_review-log.mdsaysOperator reviewed: YES(matched in the bold form the log actually writes).scripts/trial-run.shgainsACCEPT_ASSUMPTIONS=1for fixture plans. Two new conformance fixtures.🤖 Generated with Claude Code