---
name: spec-consensus
description: Merge multiple model-generated specs into one implementation-ready consensus spec.
---

# Spec Consensus

Inputs:

- multiple candidate specs
- repo context
- critique notes

Task:
Produce one consensus spec.

Method:

1. Identify agreements across specs.
2. Identify true disagreements.
3. Prefer the option that:
   - preserves existing contracts
   - minimizes change scope
   - best matches local patterns
   - is easiest to verify
4. Reject speculative abstractions.
5. Carry forward only one explicit interface design.

Output:

- consensus problem statement
- chosen design
- rejected alternatives
- frozen file scope
- frozen contract surfaces
- invariants
- verification plan

Do not average ideas together.
Choose the most stable, least surprising design.