gpt-5-4-prompting

# GPT-5.4 Prompting Use this skill when `codex:codex-rescue` needs to ask Codex or another GPT-5.4-based workflow for help. Prompt Codex like an operator, not a collaborator. Keep prompts compact and block-structured with XML tags. State the task, the output contract, the follow-through defaults, and the small set of extra constraints that matter. Core rules: - Prefer one clear task per Codex run. Split unrelated asks into separate runs. - Tell Codex what done looks like. Do not assume it will infer the desired end state. - Add explicit grounding and verification rules for any task where unsupported guesses would hurt quality. - Prefer better prompt contracts over raising reasoning or adding long natural-language explanations. - Use XML tags consistently so the prompt has stable internal structure. Default prompt recipe: - `<task>`: the concrete job and the relevant repository or failure context. - `<structured_output_contract>` or `<compact_output_contract>`: exact shape, ordering, and brevity requirements. - `<default_follow_through_policy>`: what Codex should do by default instead of asking routine questions. - `<verification_loop>` or `<completeness_contract>`: required for debugging, implementation, or risky fixes. - `<grounding_rules>` or `<citation_rules>`: required for review, research, or anything that could drift into unsupported claims. When to add blocks: - Coding or debugging: add `completeness_contract`, `verification_loop`, and `missing_context_gating`. - ...