Skip to main content
command CX Codex

plan · cloudai-x — Claude Code command: what it does, how to install

Creates and maintains a structured PLAN.md file in your project root to track phases, task dependencies, and progress logs.

MIT ★ 1,424 updated 2026-10-06

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/claude-workflow-v2-plan.md
Open on GitHub

What plan does

The command coordinates project planning inside your repository using PLAN.md. When run with a task summary, it inspects your current Git branch, recent commit history, and directory layout. Then it generates phased tasks, architectural choices, and unresolved questions.

Arguments control plan updates. Passing status displays progress percentages alongside the immediate next step. Passing complete marks the active phase finished and records a completion timestamp.

Execution relies on Read, Write, and Edit tools alongside shell access for git commands.

What it helps with

  • track project roadmaps in a local PLAN.md file
  • enforce prerequisite task dependencies across phases
  • record architectural decisions and answered questions
  • monitor active phase completion progress

Example prompts for the agent

  • /plan design database migration to PostgreSQL
  • /plan status
  • /plan complete

How to install plan

Manually: put the files in place

.claude/commands/claude-workflow-v2-plan.md

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

Questions about plan

How do I install plan in Claude Code?

Place the command file at .claude/commands/claude-workflow-v2-plan.md.

What does the plan command do?

It creates and maintains a structured PLAN.md file to track project phases, dependencies, and decision logs.

What arguments does plan accept?

You can provide a task description to add work, pass status to inspect progress, or supply complete to finish the active phase.

Source text

plan.md · MIT
---
allowed-tools: Read, Write, Edit, Glob, Grep, Bash(git:*)
description: Create and maintain a structured PLAN.md for persistent task tracking. Supports phases, dependencies, and progress tracking.
argument-hint: '[plan description, "status" to show current plan, or "complete" to mark done]'
---

# Persistent Planning

Create, update, and track a structured project plan in PLAN.md.

## Context

- Existing plan: !`cat PLAN.md 2>/dev/null | head -50 || echo "No PLAN.md found"`
- Project structure: !`ls -la 2>/dev/null | head -20`
- Current branch: !`git branch --show-current`
- Recent commits: !`git log --oneline -5 2>/dev/null || echo "No commits"`

## Behavior Based on Arguments

Interpret `$ARGUMENTS` to determine the action:

### If `$ARGUMENTS` is "status" or "show":

- Read PLAN.md and display current progress
- Show completion percentage for each phase
- Highlight the next actionable task
- List any open questions or blockers

### If `$ARGUMENTS` is "complete" or "done":

- Update the current phase to "done"
- If all phases are done, add a completion timestamp
- Summarize what was accomplished

### If PLAN.md already exists and `$ARGUMENTS` is a new task/description:

- Read the existing plan
- Add the new task(s) to the appropriate phase
- Preserve all existing progress (checked items stay checked)
- Update the plan status

### If PLAN.md does NOT exist:

- Create a new PLAN.md with the structure below
- Populate based on `$ARGUMENTS` description
- Set phase to "planning"

## PLAN.md Structure

When creating or updating PLAN.md, use this exact structure:

```markdown
# Project Plan

> Status: **[planning | implementing | verifying | done]**
> Created: [date]
> Last Updated: [date]

## Objective

[Clear, concise statement of what this plan achieves]

## Tasks

### Phase 1: [Phase Name]

- [ ] Task 1.1 — [description]
  - Depends on: [nothing | task X.Y]
- [ ] Task 1.2 — [description]
  - Depends on: Task 1.1
- [x] Task 1.3 — [completed task description]
  - Depends on: nothing
  - Completed: [date]

### Phase 2: [Phase Name]

- [ ] Task 2.1 — [description]
  - Depends on: Phase 1
- [ ] Task 2.2 — [description]
  - Depends on: Task 2.1

### Phase 3: Verification

- [ ] Run all tests
- [ ] Review changes
- [ ] Update documentation

## Architecture Decisions

| Decision   | Options Considered   | Chosen   | Rationale |
| ---------- | -------------------- | -------- | --------- |
| [decision] | [option A, option B] | [chosen] | [why]     |

## Open Questions

- [ ] [Question 1 — what needs to be answered]
- [x] [Question 2 — answered: [answer]]

## Progress Log

| Date   | Update          |
| ------ | --------------- |
| [date] | [what was done] |
```

## Rules for Plan Management

1. **Never delete completed tasks** — mark them with `[x]` and add completion date
2. **Respect dependencies** — do not mark a task complete if its dependencies are incomplete
3. **Add discovered tasks** — when implementation reveals new work, add it to the appropriate phase
4. **Update status** — move through phases: planning -> implementing -> verifying -> done
5. **Log progress** — every significant update gets a Progress Log entry
6. **Keep it current** — the plan should always reflect the true state of work
7. **Track decisions** — any architectural or design decisions go in the Architecture Decisions table
8. **Resolve questions** — when open questions are answered, mark them `[x]` with the answer

## Workflow

1. Check if PLAN.md exists in the project root
2. If it exists, read it fully to understand current state
3. Based on `$ARGUMENTS`, either show status, add tasks, or update progress
4. Write the updated PLAN.md back to disk
5. Display a summary of what changed and what is next

$ARGUMENTS

© CloudAI-X · MIT · CloudAI-X/claude-workflow-v2

Similar slash commands

All slash commands for Notes, tasks and projects →

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 Affaan Mustafa Command invokes a planner sub-agent that breaks down the task into phases, assesses risks, and waits for confirmation before touching any code. CX Codex +1 ★ 6,739repo 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 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 exec-plan pproenca exec-plan manages self-contained Markdown execution plans across agent sessions for tasks touching more than three files or taking over an hour. CX Codex +1 239installs planning davila7 planning keeps markdown files for goals, findings and session progress so an agent doesn't drift off the task mid-run. CX Codex +1 712installs alan-plan tryalan-ai alan-plan walks the agent through planning: analyze the task, ask clarifying questions, draft the plan and persist it as an Alan artifact. CX Codex +1 1,800installs plan-harder am-will Turns complex requests into structured sprint plans with atomic tasks. Triggers when you tell the agent to plan harder, focusing purely on architecture and risks. CX Codex +1 1,200installs update-implementation-plan official github update-implementation-plan updates an existing implementation plan for new requirements, refactoring, package upgrades, or architecture changes. Use it when a plan needs actionable tasks and checks. CX Codex +1 11,107installs rpi-plan microsoft rpi-plan generates or updates evidence-based Markdown implementation plans with phased tracking. Useful when a task requires structured staging and optional multi-pass critique. CX Codex +1 ★ 1,627repo stars

From the same set46

The whole set →
security-scan security-scan is a command for Claude Code that checks a repository for hardcoded secrets, vulnerable dependencies, injection, XSS and weak config before a commit or PR. CX Codex +1 ★ 1,424repo stars verify-changes verify-changes executes adversarial multi-subagent verification across recent code diffs to weed out bugs and false alarms. CX Codex +1 ★ 1,424repo stars save-session-learnings The save-session-learnings command for Claude Code saves useful findings from a coding session to CLAUDE.md and AGENTS.md after debugging or a substantial task. CX Codex +1 ★ 1,424repo stars analyzing-projects analyzing-projects walks through an unfamiliar codebase step by step: stack, structure, patterns, dev commands — useful when onboarding onto a project. CX Codex +1 ★ 1,424repo stars refactor-guided refactor-guided guides structural refactoring in small steps and runs tests after each change. It keeps feature work separate from code restructuring. CX Codex +1 ★ 1,424repo stars convex-backend convex-backend is a Claude Code skill that loads Convex guidelines for TypeScript functions, schemas, validators, queries, mutations, actions, subscriptions, and file storage. It supports type-safe backend development. CX Codex +1 ★ 1,424repo stars dependency-upgrade The dependency-upgrade command for Claude Code updates packages one by one, runs tests after each upgrade, and rolls back changes on failures. CX Codex +1 ★ 1,424repo stars designing-apis designing-apis — a Claude Code skill that designs REST and GraphQL APIs: structures endpoints, defines request and response formats, configures error handling and versioning. CX Codex +1 ★ 1,424repo stars

Project sponsors

Companies that keep this analytics open