docs: codify one-slice-one-run sizing for agent issues#55
Merged
Conversation
The in-CI agent runs under a --max-turns cap; bundling two projects/ concerns into one issue can exhaust it (error_max_turns) with nothing pushed. Make "size every agent issue to one run, split otherwise" an explicit convention, with the S0a/S0b scaffold split as the worked example. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Makes the fix from the S0 turn-cap failure systemic: a short convention in
CLAUDE.mdthat everyready+agentissue is sized to one agent run (one project / one concern), and multi-project/multi-concern work is split into sequential issues.Docs-only →
risk:trivial(auto-merges on green). The companionclaude.ymlhardening (turn-cap headroom + failure surfacing) is a separaterisk:corePR.🤖 Generated with Claude Code