plan · othmanadi — Claude Code command: what it does, how to install
Starts Manus-style file-based planning for complex engineering workflows. Generates task_plan.md, findings.md, and progress.md or restores an active session.
MIT ★ 28,179 updated 2026-11-04
/plugin marketplace add OthmanAdi/planning-with-files
/plugin install planning-with-files@planning-with-filesWhat plan does
Running this command invokes the planning-with-files:planning-with-files skill and inspects existing project directories. It detects the target directory using resolve-plan-dir.sh (or resolve-plan-dir.ps1 on PowerShell). If an active directory is found, the agent reads task_plan.md, findings.md, and progress.md without rewriting earlier progress.
Starting a fresh task triggers init-session.sh to create an isolated .planning/<id>/ directory. Each file serves a distinct role: task_plan.md stores phases and decisions, findings.md holds technical discoveries, and progress.md tracks execution history. Every ### Phase N: Name heading must contain exactly one **Status:** line.
The plan layout is verified by check-complete.sh --validate. If multiple plan directories exist without a selection, the script stops with PWF_PLAN_AMBIGUOUS_V1, requiring PLAN_ID=<slug> to pinpoint the active plan.
What it helps with
- break down multi-step tasks into phases tracked in task_plan.md
- store research notes in findings.md without cluttering source code
- log ongoing agent execution details inside progress.md
- resume interrupted work sessions without overwriting active plans
Example prompts for the agent
- /plan
- /planning-with-files:plan
- Start task planning with /plan
How to install plan
1Plugin marketplace
/plugin marketplace add OthmanAdi/planning-with-files/plugin install planning-with-files@planning-with-files2Manually: put the files in place
.claude/commands/planning-with-files-plan.mdThe built-in /plan overrides a file with the same name, so the file is renamed. Call it with /planning-with-files-plan. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/plan.mdCall it with /prompts:plan. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/plan.prompt.mdManually: put the files in place
.gemini/commands/plan.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about plan
How to install plan in Claude Code?
Add the repository using /plugin marketplace add OthmanAdi/planning-with-files, then run /plugin install planning-with-files@planning-with-files.
What does the plan command do?
It coordinates file-backed session planning by managing task_plan.md, findings.md, and progress.md. This maintains structured context across execution phases.
What happens if multiple plans exist in the workspace?
The resolve-plan-dir.sh check flags PWF_PLAN_AMBIGUOUS_V1 and pauses execution. You must set PLAN_ID=<slug> so the command targets the exact plan directory.
Source text
plan.md · MIT
---
description: "Start Manus-style file-based planning. Creates task_plan.md, findings.md, progress.md for complex tasks."
---
Invoke the planning-with-files:planning-with-files skill and follow it exactly as presented to you.
Restore before creating. If `PWF_PLAN_ROOT` is set, validate it as an absolute existing project root; refuse an invalid root pin before reading or creating files. Otherwise the project root is the current directory. Resolve the selected task with `sh ${CLAUDE_PLUGIN_ROOT}/scripts/resolve-plan-dir.sh` (PowerShell: `& "$env:CLAUDE_PLUGIN_ROOT\scripts\resolve-plan-dir.ps1"`):
- A printed directory is the selected task. Resume it: read its `task_plan.md`, `findings.md`, and `progress.md` and preserve them; never overwrite existing planning files.
- Empty output with non-empty `PLAN_ID` means the plan selector was rejected. Stop and ask the user to correct the pin. Do not fall back to the root or another plan.
- Empty output where `resolve-plan-dir.sh --check-ambiguity` (PowerShell: `-CheckAmbiguity`) prints `PWF_PLAN_AMBIGUOUS_V1` means multiple plans exist without a selector. Stop and ask the user to set `PLAN_ID=<slug>`.
- Otherwise empty output is the legacy project-root convention: resume `task_plan.md` from the validated project root (`PWF_PLAN_ROOT` when set), if it exists. A valid root pin alone does not reject a legacy root plan.
Only for a new task, run the initializer from the validated project root, including when `PWF_PLAN_ROOT` points away from the host cwd: `sh ${CLAUDE_PLUGIN_ROOT}/scripts/init-session.sh` (PowerShell: `init-session.ps1`). Pass a task name for an isolated `.planning/<id>/` plan and pin the host with its printed `PLAN_ID`. `.planning/.active_plan` is a shared default; it does not bind a parallel session.
- `task_plan.md`: for phases, progress, and decisions
- `findings.md`: for research and discoveries
- `progress.md`: for session logging
Keep each `### Phase N: Name` heading with exactly one `**Status:**` line, then validate the selected plan's explicit path with `sh ${CLAUDE_PLUGIN_ROOT}/scripts/check-complete.sh --validate path/to/task_plan.md` (PowerShell: `check-complete.ps1 -Validate -PlanFile path/to/task_plan.md`). If an existing plan fails validation, report it instead of rewriting it.
Then guide the user through the planning workflow.
© OthmanAdi · MIT · OthmanAdi/planning-with-files
Similar slash commands
All slash commands for Agent setup: memory, context, orchestration →plan by other authors comes first.