clarify

To clarify ambiguous software requirements before implementation, run a mandatory four-item checklist verifying delivery method, triggers, scope, and success criteria to ensure no assumptions slip into coding.

The clarification process for vague project requests is triggered by detecting conflicting interpretations, unclear scope, or urgency keywords such as EOD, ASAP, or directives like just do it.

You should vet requirements with a pre-implementation gate to prevent wasted work by forcing precise delivery method, triggers, scope, and success criteria before any coding proceeds.

To document autonomous assumption rationale for deferred decisions, capture the justification for decisions when the user defers so future work references why a particular direction was chosen.

The best way to handle pressured just do it development requests is to invoke a mandatory clarification gate that asks triage questions and records the clarified path before touching the codebase.