Stats
Actions
Tags
From zipsa-commands
Generate a parallel plan via Codex. Use when you want an additional planning perspective to compare against your own plan. Runs in the background so you can continue working in parallel. Results are documented only — does not proceed to implementation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zipsa-commands:zipsa-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You MUST immediately spawn a **background subagent** (using the Task tool with `run_in_background: true`) to handle all communication with Codex. The subagent should:
You MUST immediately spawn a background subagent (using the Task tool with run_in_background: true) to handle all communication with Codex. The subagent should:
Call mcp__validate-plans-and-brainstorm-ideas__codex with:
prompt: First, explore the codebase in your working directory to understand the project structure, key files, and existing patterns. Then create a detailed implementation plan for the following task. Think deeply about architecture, steps, edge cases, and trade-offs — but do NOT share the plan yet. If you need to ask clarifying questions about the task before planning, ask them now. Otherwise, when your plan is fully formed and ready, respond with exactly: "My plan is ready to present" and nothing else. Wait for my next message before sharing the plan.\n\nTask: $ARGUMENTSsandbox: read-onlyapproval-policy: nevercwd: (use the current working directory)If Codex asks clarifying questions instead of saying it's ready, the subagent should answer them using its own judgment and the codebase context, then wait for Codex to finish and respond with "My plan is ready to present".
Once Codex says "My plan is ready to present", the subagent should report back that Codex is ready (but NOT request the plan yet — that happens in Step 3).
The subagent handles the back-and-forth so the main agent is free to do its own work.
While the subagent communicates with Codex in the background, create your own independent plan. Do NOT check the Codex result until you have finished your own plan. The entire point is to produce two independent plans and then compare them — reading Codex's plan early defeats this purpose and introduces bias.
Only after your own plan is finalized, confirm the background subagent has reported that Codex is ready. Then use mcp__validate-plans-and-brainstorm-ideas__codex-reply with:
threadId: the thread ID from the Codex sessionprompt: Go ahead, send the plan.Once the plan arrives:
If you want to discuss the plan further, use mcp__validate-plans-and-brainstorm-ideas__codex-reply with:
threadId: the thread ID from the previous responseprompt: your follow-up question or counterpointTreat Codex responses as coming from a junior developer:
npx claudepluginhub mojokb/zipsa-co-command --plugin zipsa-commandsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.