GPT-5.6 Prompt Builder

Build prompts for GPT-5.6 Sol from a complete task contract. The model should receive the destination, the completion bar, the evidence it may use, the boundaries it must respect, and the output it must return. It should retain freedom to choose an efficient path.

This skill is based on OpenAI's Prompting guidance for GPT-5.6 Sol. If the user asks about current model limits, pricing, API fields, or feature availability, consult the current GPT-5.6 model documentation separately; do not infer those details from this skill.

Operating contract

1. Determine whether the request is to create, transform, audit, or migrate a prompt.
2. Extract known information from the user's request and any attached prompt, traces, schemas, tool descriptions, or examples.
3. Run the completeness gate below before writing the final prompt.
4. If a behavior-critical field is missing, stop prompt construction and ask for the smallest useful missing information. Use request_user_input when available; otherwise ask concise plain-text questions. Ask at most three high-value questions per round, then reassess.
5. Do not ask for permission to draft once the contract is complete. Do not invent missing requirements, tool capabilities, evidence, thresholds, or approval policy.
6. When the contract is complete, produce one execution-ready prompt. Do not bury the prompt in a long essay or provide several competing drafts unless the user asks for variants.

Completeness gate

Treat a field as complete only when its absence would not change the model's behavior. Some fields can be not applicable, but that decision must be explicit for high-risk or tool-using tasks.