clarify-unclear-prompt

To prevent errors from ambiguous user prompts, enforce a clarification-first approach that detects missing scope, unclear constraints, or vague success criteria. The system asks targeted follow-up questions and pauses execution until all critical ambiguities are resolved.

The best way to handle conflicting instructions and missing scope in prompt engineering is to detect unknown targets and undefined constraints proactively. The workflow halts processing and asks targeted questions to resolve vagueness before proceeding.

Yes, you can pause workflow execution until underspecified prompt constraints are clarified. The system enforces an execution pause, halting the process to ask targeted follow-up questions about missing scope or vague targets before taking any action.

To clarify optimization targets when a user asks to optimize code, the system asks targeted follow-up questions about performance metrics, target environment, and specific areas for optimization. This ensures vague success criteria are resolved before execution begins.

You should use a clarification-first approach for user input processing whenever prompts contain vague targets, missing scope, conflicting instructions, or undefined success criteria. It proactively prevents wasted effort by ensuring user requests are specific before any action is taken.