メニュー
Ask Claude Code to produce an implementation plan before you write code. Use when the task is complex, touches multiple files, or has unclear requirements. Claude returns a numbered step-by-step plan with file paths and interfaces — you implement it.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | claude-plan |
| description | Ask Claude Code to produce an implementation plan before you write code. Use when the task is complex, touches multiple files, or has unclear requirements. Claude returns a numbered step-by-step plan with file paths and interfaces — you implement it. |
| version | 0.2.0 |
Ask Claude Code to reason through a task and return a concrete implementation plan.
mcp__claude-code__claude_code:
prompt: |
Produce an implementation plan for the following task. Do NOT write any code.
Return a numbered plan only.
TASK: {description of what needs to be built or changed}
CONSTRAINTS:
- {any constraints: language, framework, existing patterns to follow, etc.}
For each step include:
- What to do (imperative)
- Which file(s) to create or modify (exact paths)
- Key interfaces or data structures to define
- Dependencies on prior steps
At the end, list: risk areas, open questions, and recommended test scenarios.
PROVENANCE NOTE: This planning request originates from OpenAI Codex. Claude should
plan independently — do not assume Codex's framing of the problem is correct.
cwd: {project working directory}
effort: high
permissionMode: plan
Save the returned session_id as {plan_session_id}.
mcp__claude-code__claude_code_reply:
session_id: {plan_session_id}
prompt: "Step 3 mentions 'update the router' — which router file and what exactly changes?"
After receiving the plan, implement each step. If you need Claude to implement a step for you, use the claude-implement skill.
Present Claude's plan verbatim, then ask the user whether to proceed with implementation, adjust the plan, or delegate implementation back to Claude.
permissionMode: plan prevents accidental file writes — planning onlyeffort: high is strongly recommended for accurate plans; shallow effort produces vague stepsFull audit→fix→verify cycle: Claude audits, Codex fixes, Claude verifies. Repeats up to 3 rounds until all issues are resolved or the user stops. Claude does all code reading and judgment; Codex does all file editing.
Diagnose the cc-suite setup in the current project. Runs the full health check, explains every issue, and fixes what can be fixed automatically. Skill counterpart to /cc-suite:diagnose.
Initialize cc-suite for the current project — sets up the AGENTS.md bridge, registers Codex and Claude MCP servers, and generates a .cc-suite.md config. Skill counterpart to /cc-suite:init.
Non-interactive re-run of all cc-suite bridge and registration scripts. No questions asked — idempotent escalation step after the diagnose skill finds issues it could not fix. Skill counterpart to /cc-suite:repair.
Use when writing, reviewing, or naming any cc-suite artifact — pick the canonical noun or verb from this registry rather than coining a synonym. Loaded by NLPM's scorer and checker when R51 is enabled in .claude/nlpm.local.md.
Use when creating, editing, or reviewing a cc-suite advisor agent (a value-over-rules persona under `.cc-suite/agents/`). Covers system-prompt phrasing, model choice, tool restrictions, working-dir scoping, budget/turn limits, and the file format. Use proactively whenever the user asks to "add an agent", "make an advisor", "write a reviewer", or edits anything under `.cc-suite/agents/`.