Repository navigation
feat(meta-mode): settle contested designs with evidence, not interrogate - #59
Merged
Merged
Conversation
Adversarial review spends tokens on nitpicks and YAGNI findings. Route contested designs to a prototype, blast-radius, statechart, or formal verification instead, and run interrogate only when the user asks for an adversarial review. The interrogate skill itself is unchanged. Updates meta-mode, the Feature, Bug fix, and Multi-phase plan playbooks, architect, mstack-help, and the design guide (through a recorded guide replacement), then refreshes the skill and canonical baselines. 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.
Why
meta-mode routes every contested design to
interrogatebefore shipping. In practice, abstract multi-model review spends tokens on nitpicks and YAGNI findings. pstack's author has said they are moving pstack away frominterrogatefor this reason and toward empirical plus formal verification. This change makes the same shift in mstack ahead of the upstream sync.What changed
Contested designs now settle on evidence: a prototype or
blast-radiusfor behavior, andstatechartor formal verification for state, protocol, and concurrency invariants.interrogatestays installed and still runs when the user asks for an adversarial review. Updated places: meta-mode's trigger list, the Feature, Bug fix, and Multi-phase plan playbooks,architect,mstack-help, and the design-ladder bullets indocs/guide/04-design.md. The guide edit is recorded as an upstream replacement inprofiles/upstreams.json. The skill and canonical baselines are refreshed.Verification
npm test: 723 pass, 0 fail.check-upstream --strictagainst pstack at the pinned4dd1d05passes. Editing the guide without its replacement makes the check fail withchanged: docs/guide/04-design.md, so the replacement is what keeps it green.skill-baseline --diffreported exactly the six edited skill files.Agent: Claude Opus 5.5 via Claude Code
🤖 Generated with Claude Code