prompt-technique-router

The best way to choose a prompting technique is to match the task shape—ambiguous, structured, retrieval-grounded, or tool-dependent—and apply the lightest effective method to avoid overengineering while ensuring structured output.

To refactor a raw prompt for structured output, route it to a fitting technique like structured reasoning, rewrite it with clear constraints and inputs, then generate a validation report covering ambiguity handling and risk gating.

You need retrieval-grounded or tool-loop prompting when your task depends on external data sources or specific tool interactions, shifting away from zero-shot to handle complex, dependent scenarios with fallback guidance.

Prompt routing prevents prompt overengineering by selecting the lightest effective technique for the specific task shape, validating the refactored prompt for minimality, and providing operator notes to avoid unnecessary complexity.

If your refactored prompt fails validation checks, use the provided fallback guidance and operator notes to address failure modes, handle missing context, or adjust the technique selection to better fit the risk level and constraints.