refactor: add failure conditions to plan output#770
Merged
Conversation
Plan now defines 5 things: domain constraints, realistic usage, test queries, evaluation (success + failure conditions + restart points), and role division. Key changes: - New "Failure Conditions" section in plan output: hard reject rules derived from domain constraints, with which expert caused the failure and where to restart - Success Criteria no longer includes "what failure looks like" (moved to dedicated Failure Conditions section) - Failure conditions are not the inverse of success criteria — they are domain-specific rules that require deep understanding of constraints Co-Authored-By: Claude Opus 4.6 <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
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.
Summary
Test plan
bun run testpasses🤖 Generated with Claude Code