Menü
Show plugin-dev status and explain sync workflow
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Invoke OpenAI Codex CLI for cross-model collaboration
Claude Code only. Use when the user explicitly invokes /agents-bridge:codex-orchestrate (or /codex-orchestrate) in Claude Code or asks Claude to orchestrate a large multi-slice plan by delegating implementation to the Codex CLI through agents-bridge. In native Codex, use $slice-runner instead.
Critical second opinion from Codex (OpenAI) on a proposal Claude just made — confirms what is sound, challenges what is genuinely weak, and suggests a better path with clear reasoning when one exists. Constructive, not contrarian. Use to cross-check a Claude design, refactor, API, or fix with a non-Claude model before acting on it.
Start a session in pair-planning mode where Claude and Codex (read-only) each draft an independent implementation plan for a task, then cross-review through an open-point ledger until consensus, escalating remaining disagreements to the user. Produces one agreed plan; does not write code. Use at the start of a task to align two frontier models on the approach before implementation.
Audits CLAUDE.md and AGENTS.md files against research-backed best practices: instruction budget scoring, anti-pattern detection, staleness checks, and concrete fix proposals. Use when the user asks to audit, check, review, or optimize context files, or mentions "instruction budget" or "context file quality". Treats CLAUDE.md and AGENTS.md identically.
Synchronizes project CLAUDE.md with recent codebase changes by analyzing git history, reviewing against official Anthropic best practices with parallel agents, and proposing updates for user approval. Use when CLAUDE.md is outdated, missing, or drifted after major architectural changes.
| name | plugin-dev-usage |
| description | Show plugin-dev status and explain sync workflow |
| allowed-tools | ["Bash(*:*)","Read(*:*)"] |
Dev tool for syncing Claude Code plugin cache from local sources.
!"${CLAUDE_PLUGIN_ROOT}/scripts/plugin-dev" version 2>&1 || echo "(plugin-dev not available)"
!"${CLAUDE_PLUGIN_ROOT}/scripts/plugin-dev" status 2>&1 || echo "(could not get status)"
plugin-dev status — shows which plugins are stale and which are enabledplugin-dev sync <name> — partial name match (e.g. plugin-dev sync meta)plugin-dev sync --allplugin-dev enable <name> (or --all) — sync does not touch settings.json, so a brand-new plugin must be enabled once before Claude Code will load it (disable to turn off)/reload-plugins is not sufficient)
syncwarns when a plugin is synced but not enabled. Enabling writes the live~/.claude/settings.json(the same file/pluginwrites).
For repos not registered as a known marketplace:
$PWD/.claude-plugin/marketplace.json exists, plugin-dev uses it automaticallyplugin-dev --source /path/to/repo sync --allRun /plugin-dev:install to add plugin-dev to your PATH.
On Windows, run /plugin-dev:update after plugin updates to re-copy the script.
| Path | Purpose |
|---|---|
~/.claude/plugins/cache/ | Plugin cache (what plugin-dev syncs) |
~/.claude/plugins/installed_plugins.json | Installed plugin registry |
~/.claude/plugins/known_marketplaces.json | Marketplace sources |