Repository navigation
feat(plan): blind second opinion for high-stakes tasks (#117) - #126
Merged
Merged
Conversation
For tasks tagged model="opus" or touching a CRITICAL.md path (max 2 per phase), plan records the options weighed and spawns one Opus agent that writes its own approach before reading the plan's, then compares. Only a real disagreement asks the user, once, before build; autonomous pauses on it; build asks about any left pending. Closes #117 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.
Closes #117.
What changes, in plain terms
For the few plan tasks that are expensive to undo (data model, sync, payments, migrations), a second agent now works out its own approach before it sees the plan's, then says: same / different but fine / "the plan's choice is worse because …".
model="opus"or touching aCRITICAL.mdpath. At most 2 per phase; never ordinary UI or feature tasks.<options>with the chosen one and the rejected ones with why.<second-opinion>line.resolved="pending", and pauses before building that phase (not skipped by--yes).buildasks about any left pending, and passes<options>to the builder so it doesn't drift to a rejected one.Checks
./scripts/validate.shpasses.🤖 Generated with Claude Code