Repository navigation
feat: have scode-build-goal plans weigh reuse against duplication - #532
Merged
Merged
Conversation
The planning review and scope reassessment only asked whether a plan did more than the user needs. A plan could pass that test by staying small through copying a mechanism the repository already has, which moves the cost to whoever has to keep the two copies in step later. The opposite pull goes wrong too, by generalizing an existing mechanism for uses nobody asked for, so the skill now has the planner weigh the two instead of letting either win. Clear-cut cases stay the planner's to settle. Close calls go to the user during planning. Otherwise the unattended run would end up making them without the user. Co-Authored-By: Claude Opus 5.5 <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.
The planning review and scope reassessment only asked whether a plan did more than the user needs. A plan could pass
that test by staying small through copying a mechanism the repository already has, which moves the cost to whoever has
to keep the two copies in step later. The opposite pull goes wrong too, by generalizing an existing mechanism for uses
nobody asked for, so the skill now has the planner weigh the two instead of letting either win.
Clear-cut cases stay the planner's to settle. Close calls go to the user during planning. Otherwise the unattended run
would end up making them without the user.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com