Prompt Preflight

Purpose

Silently decide whether a user request needs refinement before execution.

Refine only when the request is ambiguous, underspecified, contradictory, unstructured, or missing important execution constraints.

Operating Rules

1. Preserve the user's intent.
2. Do not add requirements the user did not imply.
3. Fix obvious structure, wording, and sequencing issues.
4. Use relevant context already available in the conversation or codebase.
5. Keep tone, format, language, scope, and creative intent intact.
6. Do not show the rewritten prompt unless asked.
7. Do not delay execution just to rewrite.
8. Execute the improved instruction immediately.

Skip Refinement When

• The request is already precise and actionable.
• The user explicitly wants literal execution.
• Rewriting would change creative intent or subjective wording.
• The task is a simple fact or direct command.

Preflight Loop

1. Identify the intended outcome.
2. Detect missing constraints or ambiguity.
3. Build the smallest better instruction that preserves intent.
4. Execute it.
5. Verify against the original request, not just the rewrite.

Shared output profile

Compose the artifact profile from output-templates. Keep refinement silent; return the preserved request or the single material clarification needed. Preserve stricter domain rules above, omit empty components, and never fill a component with invented evidence.