requirement-convergence

Requirement Convergence

Purpose

Capable models can make an oversized or misdirected request technically coherent and implement it faithfully. Converge what is worth building before design decides how to build it.

Apply this skill to future-state Design Doc and implementation flows. Reverse-engineered/as-is documentation is outside its scope. Requirement Convergence decides what to build; implementation-approach decides the smallest sufficient way to build the converged scope.

Convergence Record

Field	Pass condition
outcome	One observable result. Every buildable requirement serves it.
requirements[]	Every item is labeled current-state, desired-future, or speculative.
nonGoals[]	The user decided each exclusion or explicitly stated there are none.
cost	A rough band with structural evidence and remaining unknowns.

cost is an early requirements estimate, not a design or work-plan estimate. It is intentionally approximate: enough to challenge low-value scope without pretending shallow inspection can produce exact effort.

All four fields apply whenever Requirement Convergence runs. Each field has readiness ready, weak, or weak-but-explicit. Only the user can accept weak-but-explicit. The record is converged when every field is ready or weak-but-explicit.

Use references/criteria.md to judge each field.

Hearing Protocol

The orchestrator owns user interaction. It runs the hearing after an analysis step has produced scope facts.

1. Present observed scope facts separately from their inferred implications.
2. Ask only about fields below ready, at most two questions per message.
3. Record answers in the user's wording.
4. If an answer still fails its pass condition, ask once more. Mark it weak-but-explicit only when the user agrees to proceed unresolved.
5. Re-judge the updated record before design begins. Re-run structural analysis only when an answer changes scope or cost evidence; otherwise the orchestrator applies the field's pass condition directly.