From codex-collab
This skill should be used when the user wants to "plan with Codex", "create a plan", "draft implementation plan", "help me plan", "plan before implementing", "refine a plan", "review my plan idea", "Codexと計画を立てる", "実装計画を作成", "計画を立てたい", "計画を一緒に考えて", "実装方針を相談", "Codexと設計を練る", "計画だけ作りたい", "実装前に計画を立てたい", "計画をレビューしてほしい", or mentions creating/refining an implementation plan as the deliverable without proceeding to implementation. NOTE: This is for PLAN-ONLY workflows that produce a plan document as the deliverable. Do NOT use when the user wants implementation (use codex-collab instead). Do NOT use for adversarial design critique (use devils-advocate instead). Do NOT use for debugging (use strong-inference instead).
npx claudepluginhub masup9/codex-collab --plugin codex-collabThis skill uses the workspace's default tool permissions.
Create and refine implementation plans through collaborative iteration between Claude and Codex. **Plans only — no implementation.**
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Create and refine implementation plans through collaborative iteration between Claude and Codex. Plans only — no implementation.
Collaborative Planning produces a polished implementation plan by:
Key constraint: This skill NEVER starts implementation. The deliverable is always a plan document.
| Aspect | collab-planning | codex-collab | devils-advocate |
|---|---|---|---|
| Purpose | Create/refine plans only | Plan + implement + review | Stress-test a design |
| Implementation | Never | Yes (Claude or Codex) | No |
| Deliverable | Plan document (fixed template) | Implemented code | Verdict (APPROVE/CONDITIONAL/REJECT) |
| Claude's role | Context collection + draft | Implementation or review | Blue Team advocate |
| Codex's role | Plan review + improvement | Planning or implementation | Red Team critic |
| Use case | Pre-implementation planning | End-to-end task execution | Design validation |
codex exec) or MCP configuredClaude gathers information:
Claude creates an initial plan using the fixed template:
Codex reviews the plan and provides:
good / needs-improvement / major-revisionBased on quality assessment:
good → Finalize and present to userneeds-improvement → Claude refines, re-submit to Codexmajor-revision → Ask user for direction, then re-draft or concludePresent the polished plan in the fixed template format.
.claude/codex-collab.local.md)collab_planning:
max_iterations: 3 # Review improvement cycle limit
user_confirm: on_important # never | always | on_important
Existing settings (model, sandbox, language) are also respected.
Use the /collab-planning command:
# Basic usage
/collab-planning Add pagination to the user list API
# With options
/collab-planning --max-iterations 5 Refactor authentication module
# Japanese
/collab-planning ユーザーリストAPIにページネーションを追加する計画を立てたい
Detailed templates in references/:
plan-draft-guide.md - Fixed template for plan documentsplan-review-prompt.md - Template for Codex review requests