| name | pi-autoreason |
| description | Run or design Autoreason-style refinement in Pi. Use when refining bounded artifacts, source-grounded PDF/book/manual extractions, PRDs, plans, prompts, or other documents where "do nothing" must remain a first-class option. Avoid for unbounded brainstorming or direct code edits unless a human explicitly accepts the cost and risk. |
| disable-model-invocation | true |
pi-autoreason
Use pi-autoreason for structured self-refinement based on the Autoreason paper.
Core loop
Each pass compares:
A: unchanged incumbentB: adversarial revision from a critic's concrete problemsAB: synthesis of A and B
Fresh judges rank randomized versions. Borda count chooses the winner. Ties go to A. Stop when A wins k=2 consecutive passes.
When to use
Good fits:
- bounded plans, PRDs, specs, implementation prompts
- source-derived text where source faithfulness matters
- docs with real tradeoffs and enough constraints
- mid-tier model workflows where generation is decent but selection is weak
Bad fits:
- vague “make it better” requests with no constraints
- template-filling where conservative editing is enough
- direct code edits without tests or explicit acceptance
- source-derived educational content unless source-grounded mode is used
Source-grounded law
