Skip to main content
command CX Codex

plan · worldflowai — Claude Code command: what it does, how to install

Command invokes a planner sub-agent that breaks down the task into phases, assesses risks, and waits for confirmation before touching any code.

MIT ★ 6,739 updated 2026-01-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add WorldFlowAI/everything-claude-code
/plugin install everything-claude-code@everything-claude-code
Open on GitHub

What plan does

The /plan command starts the planner sub-agent, which restates requirements, divides work into phases (DB schema, service, integration, frontend), lists dependencies (Redis, email service, Supabase subscriptions), and estimates complexity. Risks are marked HIGH, MEDIUM, or LOW — for instance, HIGH for email deliverability without SPF/DKIM. The agent does not modify files until it receives an explicit "yes" or "proceed".

Useful for new features, multi-component refactoring, and ambiguous requirements. Without Redis and a configured email service, examples from the plan will not run. After confirmation, continue with /tdd or /build-and-fix.

What it helps with

  • break down a large task into steps before writing code
  • identify dependencies and risks of an architectural change
  • get a time and complexity estimate for a feature
  • clarify requirements before refactoring multiple files

Example prompts for the agent

  • Plan adding real-time notifications when markets resolve
  • Break down the migration from REST to GraphQL into phases
  • Assess risks of integrating Stripe for subscriptions

How to install plan

1Plugin marketplace

/plugin marketplace add WorldFlowAI/everything-claude-code
/plugin install everything-claude-code@everything-claude-code

2Manually: put the files in place

.claude/commands/everything-claude-code-plan.md

The built-in /plan overrides a file with the same name, so the file is renamed. Call it with /everything-claude-code-plan. For all projects use ~/.claude/commands/

Questions about plan

How to install plan in Claude Code?

Run /plugin marketplace add WorldFlowAI/everything-claude-code, then /plugin install everything-claude-code@everything-claude-code. The command will appear in .claude/commands/everything-claude-code-plan.md.

What does the plan command do?

Invokes a planner sub-agent that restates the task, breaks it into phases, lists dependencies and risks, estimates complexity, and waits for your confirmation. Code is not changed until an explicit "yes".

Can I modify the plan before execution?

Yes. Write "modify: your changes" or "skip phase 2 and do phase 3 first". The agent will rebuild the plan and ask for confirmation again.

Source text

plan.md · MIT
---
description: Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.
---

# Plan Command

This command invokes the **planner** agent to create a comprehensive implementation plan before writing any code.

## What This Command Does

1. **Restate Requirements** - Clarify what needs to be built
2. **Identify Risks** - Surface potential issues and blockers
3. **Create Step Plan** - Break down implementation into phases
4. **Wait for Confirmation** - MUST receive user approval before proceeding

## When to Use

Use `/plan` when:
- Starting a new feature
- Making significant architectural changes
- Working on complex refactoring
- Multiple files/components will be affected
- Requirements are unclear or ambiguous

## How It Works

The planner agent will:

1. **Analyze the request** and restate requirements in clear terms
2. **Break down into phases** with specific, actionable steps
3. **Identify dependencies** between components
4. **Assess risks** and potential blockers
5. **Estimate complexity** (High/Medium/Low)
6. **Present the plan** and WAIT for your explicit confirmation

## Example Usage

```
User: /plan I need to add real-time notifications when markets resolve

Agent (planner):
# Implementation Plan: Real-Time Market Resolution Notifications

## Requirements Restatement
- Send notifications to users when markets they're watching resolve
- Support multiple notification channels (in-app, email, webhook)
- Ensure notifications are delivered reliably
- Include market outcome and user's position result

## Implementation Phases

### Phase 1: Database Schema
- Add notifications table with columns: id, user_id, market_id, type, status, created_at
- Add user_notification_preferences table for channel preferences
- Create indexes on user_id and market_id for performance

### Phase 2: Notification Service
- Create notification service in lib/notifications.ts
- Implement notification queue using BullMQ/Redis
- Add retry logic for failed deliveries
- Create notification templates

### Phase 3: Integration Points
- Hook into market resolution logic (when status changes to "resolved")
- Query all users with positions in market
- Enqueue notifications for each user

### Phase 4: Frontend Components
- Create NotificationBell component in header
- Add NotificationList modal
- Implement real-time updates via Supabase subscriptions
- Add notification preferences page

## Dependencies
- Redis (for queue)
- Email service (SendGrid/Resend)
- Supabase real-time subscriptions

## Risks
- HIGH: Email deliverability (SPF/DKIM required)
- MEDIUM: Performance with 1000+ users per market
- MEDIUM: Notification spam if markets resolve frequently
- LOW: Real-time subscription overhead

## Estimated Complexity: MEDIUM
- Backend: 4-6 hours
- Frontend: 3-4 hours
- Testing: 2-3 hours
- Total: 9-13 hours

**WAITING FOR CONFIRMATION**: Proceed with this plan? (yes/no/modify)
```

## Important Notes

**CRITICAL**: The planner agent will **NOT** write any code until you explicitly confirm the plan with "yes" or "proceed" or similar affirmative response.

If you want changes, respond with:
- "modify: [your changes]"
- "different approach: [alternative]"
- "skip phase 2 and do phase 3 first"

## Integration with Other Commands

After planning:
- Use `/tdd` to implement with test-driven development
- Use `/build-and-fix` if build errors occur
- Use `/code-review` to review completed implementation

## Related Agents

This command invokes the `planner` agent located at:
`~/.claude/agents/planner.md`

© Affaan Mustafa · MIT · WorldFlowAI/everything-claude-code

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

plan by other authors comes first.

plan OthmanAdi Loads the planning-with-files skill and starts planning in the current project. Handy when you want to begin a new plan or continue an existing one. CX Codex +1 ★ 28,179repo stars plan OthmanAdi Starts Manus-style file-based planning for complex engineering workflows. Generates task_plan.md, findings.md, and progress.md or restores an active session. CX Codex +1 ★ 28,179repo stars plan disler Turns a task description into a step-by-step implementation plan saved under specs/. Useful when a feature needs thinking through before any code. CX Codex +1 ★ 3,990repo stars plan CloudAI-X Creates and maintains a structured PLAN.md file in your project root to track phases, task dependencies, and progress logs. CX Codex +1 ★ 1,424repo stars plan OthmanAdi Creates task_plan.md, findings.md and progress.md in the project root, so the goal, research and session log sit next to the code. CX Codex +1 ★ 540repo stars ce-plan EveryInc ce-plan builds structured technical implementation plans without touching production code. Useful when scoping features before passing work to execution agents. CX Codex +1 4,000installs speckit-plan github-spec-kit speckit-plan executes implementation planning workflows inside spec-kit projects to produce research notes and interface contracts. CX Codex +1 2,600installs re0-plan LilMGenius The re0-plan Claude Code skill creates a paperthin iteration folder and seeds it with planning files. It runs on request when a new build cycle starts in the repository. CX Codex +1 1,400installs plan-task NeoLabHQ plan-task turns a rough task spec into a plan with acceptance criteria, an architecture overview and verifiable phases, each gated by a judge. CX Codex +1 1,300installs to-plan chrisbanes to-plan turns one GitHub issue or an in-chat task into an implementation plan with acceptance criteria. Useful when the work has to be handed to someone else. CX Codex +1 884installs create-plan davila7 create-plan turns a prompt into one actionable plan with a checklist. Useful when you want the steps agreed before any code changes. CX Codex +1 852installs

From the same set29

The whole set →
setup-pm setup-pm — a command to configure which package manager (npm, pnpm, yarn, or bun) Claude Code uses in your project or globally. Use it when you want to enforce a specific manager across your workflow. CX Codex +1 ★ 6,739repo stars code-reviewer The code-reviewer subagent reviews code changes for security vulnerabilities, bugs, performance problems, and style violations. Run it immediately after writing or modifying code to catch issues before they reach production. CX Codex ★ 6,739repo stars planner planner generates structured implementation plans and refactoring roadmaps for Claude Code projects. CX Codex ★ 6,739repo stars orchestrate orchestrate routes a complex task through a sequence of agents and combines their findings into a report. Choose a workflow for a feature, bug fix, refactor, or security review. CX Codex +1 ★ 6,739repo stars architect An opus-powered subagent for designing scalable software architecture, analyzing technical trade-offs, and drafting Architecture Decision Records. CX Codex ★ 6,739repo stars tdd-guide The tdd-guide subagent guides feature work, bug fixes, and refactoring through a test-first workflow. It also checks test coverage against an 80% target. CX Codex ★ 6,739repo stars refactor-cleaner refactor-cleaner is a Claude Code subagent that finds and removes unused code, duplicates, and dependencies. It runs knip, depcheck, and ts-prune during codebase cleanup. CX Codex ★ 6,739repo stars tdd tdd enforces a strict test-driven development cycle in Claude Code by writing failing tests first, implementing minimal code, and checking for 80%+ coverage. CX Codex +1 ★ 6,739repo stars

Project sponsors

Companies that keep this analytics open