clarify-and-specify

name	clarify-and-specify
description	Resolve material product, behavior, scope, interface, migration, or acceptance decisions that evidence cannot safely determine. Use only while such decisions remain unresolved, not merely because work is large or multi-stage.

Clarify and Specify

1. Inspect the available project, documentation, and surrounding implementation before asking questions. Resolve facts through evidence and do not trigger this workflow solely because a request is large or multi-stage.
2. Identify the objective, users, current and desired behavior, constraints, non-goals, dependencies, risks, and observable acceptance criteria. Expose only assumptions that would materially change the solution.
3. Ask the smallest set of decision-bearing questions. Ask about decisions only; let evidence, established defaults, or implementation judgment settle facts and minor details.
4. Produce one coherent specification containing scope, behavior, interfaces or data changes, failure behavior, compatibility requirements, validation, and acceptance criteria. Keep implementation details open when several approaches remain valid.
5. Request explicit approval only when a material decision remains unresolved or a proposed irreversible consequence was not already named and authorized. Treat an explicitly authorized action as settled unless new evidence changes its effect or risk. Incorporate corrections into the specification rather than appending contradictory notes.

Finish when a new implementer could determine what is in scope and prove completion without guessing.