openai / openai/codex-plugin-cc

Make gpt-5-4-prompting skill model-neutral and multi-agent aware

Open
#463 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
33.3k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

The bundled gpt-5-4-prompting skill is model-labeled and says it applies to GPT-5.4 workflows, while current Codex installations may use newer models and bounded multi-agent execution.

Suggested update:

  • Rename the skill and metadata to a version-neutral Codex prompting name.
  • Keep the useful compact contract blocks: task, output contract, grounding, safety, and verification.
  • Replace the single-run bias with guidance for bounded parallel lanes when audit or exploration surfaces are independent.
  • Require the lead agent to reproduce or verify accepted child-agent findings before reporting them.
  • Describe the concrete benefit: less stale model routing, fewer missed independent surfaces, and faster broad reviews without weakening evidence requirements.

The current skill text itself is still useful; this request is about making its scope and orchestration guidance match current Codex capabilities.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the bundled gpt-5-4-prompting skill and its metadata, then review every reference to the model-specific name and single-run workflow. Done means the skill is version-neutral, preserves the listed contract blocks, explains bounded independent parallel lanes, and requires lead-agent verification of accepted findings.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
developer-experience, documentation, tooling
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.