plan-ar
Commandبدء تخطيط الملفات بنمط Manus. إنشاء task_plan.md و findings.md و progress.md للمهام المعقدة.
@othmanadiInstall CommandDevelopment
Command
/plan
Start Manus-style file-based planning. Creates task_plan.md, findings.md, progress.md for complex tasks.
> /plugin marketplace add OthmanAdi/planning-with-files> /plugin install planning-with-files@planning-with-files
Command definition
plan.mddescription: "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.
Read more
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.
Ships withplanning-with-files
Persistent file-based planning for AI coding agents and long-running tasks. Crash-proof markdown plans, session recovery after /clear and compaction, per-turn re-injection against context rot, deterministic completion gate. Manus-style. Install from npm, the Claude Code plugin marketplace, or npx skills. Codex, Cursor, OpenCode, 60+ agents.
28k6 skills
Stars on GitHub
Momentum
- stars in total
- 27.8k
Other commands on planning-with-files.
@othmanadiInstall Commandplan-attest
CommandLock the current task_plan.md content with a SHA-256 attestation. Hooks then refuse to inject plan content if the file diverges…
@othmanadiInstall Commandplan-de
CommandStarte Manus-artige Dateiplanung. Erstelle task_plan.md, findings.md, progress.md für komplexe Aufgaben.
@othmanadiInstall Commandplan-doctor
CommandSelf-check for the planning-with-files mechanisms that fail silently: plan resolution, hook injection, canonicalizer path shape,…
@othmanadiInstall Commandplan-es
CommandIniciar planificación de archivos estilo Manus. Crear task_plan.md, findings.md, progress.md para tareas complejas.
@othmanadiInstall Commandplan-goal
CommandBridge Claude Code's /goal to the active plan. Derives a goal condition from task_plan.md and invokes /goal so Claude keeps…
@othmanadiInstall CommandMore commands from other plugins.
Auto-invoked
Auto-invoked
build
CommandImplement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
@addyosmaniInstall Command