gpt-5-4-prompting
Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Codex Claude Code plugin
What this skill does
# 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`. - Review or adversarial review: add `grounding_rules`, `structured_output_contract`, and `dig_deeper_nudge`. - Research or recommendation tasks: add `research_mode` and `citation_rules`. - Write-capable tasks: add `action_safety` so Codex stays narrow and avoids unrelated refactors. How to choose prompt shape: - Use built-in `review` or `adversarial-review` commands when the job is reviewing local git changes. Those prompts already carry the review contract. - Use `task` when the task is diagnosis, planning, research, or implementation and you need to control the prompt more directly. - Use `task --resume-last` for follow-up instructions on the same Codex thread. Send only the delta instruction instead of restating the whole prompt unless the direction changed materially. Working rules: - Prefer explicit prompt contracts over vague nudges. - Use stable XML tag names that match the block names from the reference file. - Do not raise reasoning or complexity first. Tighten the prompt and verification rules before escalating. - Ask Codex for brief, outcome-based progress updates only when the task is long-running or tool-heavy. - Keep claims anchored to observed evidence. If something is a hypothesis, say so. Prompt assembly checklist: 1. Define the exact task and scope in `<task>`. 2. Choose the smallest output contract that still makes the answer easy to use. 3. Decide whether Codex should keep going by default or stop for missing high-risk details. 4. Add verification, grounding, and safety tags only where the task needs them. 5. Remove redundant instructions before sending the prompt. Reusable blocks live in [references/prompt-blocks.md](references/prompt-blocks.md). Concrete end-to-end templates live in [references/codex-prompt-recipes.md](references/codex-prompt-recipes.md). Common failure modes to avoid live in [references/codex-prompt-antipatterns.md](references/codex-prompt-antipatterns.md).
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.