plan-loop
The plan-loop command runs a recurring planning-aware task loop using Claude Code's /loop primitive, with configurable intervals and custom or default prompts. Use it to automatically monitor project progress by periodically checking task_plan.md, running completion checks, and updating progress.md without manual intervention, particularly when combined with /plan-goal for automatic termination once planning objectives are met.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/OthmanAdi/planning-with-files/HEAD/commands/plan-loop.md -o ~/.claude/commands/plan-loop.mdplan-loop.md
Run a planning-aware cadence on top of Claude Code's `/loop` primitive.
Steps:
1. Parse args:
- First arg matching `^\d+[smhd]$` is the interval (default `10m`).
- Remaining args are an optional task prompt.
2. Resolve the active plan as in `/plan-attest`.
3. Compose the loop prompt:
- If user passed a task prompt: use it verbatim.
- Else: use the default planning tick prompt:
```
Read task_plan.md and progress.md. Run scripts/check-complete.sh to see remaining phases.
If no progress.md entry has been added since the last loop tick, write one summarizing the current state.
If a phase finished, update its Status: line in task_plan.md.
Continue the next phase if work remains.
```
4. Invoke `/loop <interval> <prompt>`.
5. Confirm to the user: print the interval, the active plan ID, and remind that bare `/loop` invocation alone (without args) runs Claude Code's built-in maintenance prompt — `/plan-loop` differs by always grounding the tick in the planning files.
If `task_plan.md` does not exist, refuse and direct user to run `/plan` first.
Why this exists:
`/loop` runs prompts on cron without any plan-state contract. `/plan-loop` injects a plan-aware default so the recurring tick always re-reads the planning files first, runs the completion check, and writes a progress entry. Users get "babysit my plan" UX without writing a custom loop prompt.
Notes:
- `/plan-loop` composes with `/loop`; it does not replace it. `/loop 5m "anything"` still works.
- For "babysit until plan is done" semantics: combine `/plan-loop 10m` (cadence) with `/plan-goal` (termination criterion). The loop runs every 10 minutes; the goal stops the loop when the plan is complete.
- The default tick prompt is intentionally short so it stays within compaction-safe length.Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session recovery after /clear.
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session recovery after /clear.
بدء تخطيط الملفات بنمط Manus. إنشاء task_plan.md و findings.md و progress.md للمهام المعقدة.
Lock the current task_plan.md content with a SHA-256 attestation. Hooks then refuse to inject plan content if the file diverges from the attested hash, blocking silent tampering. Use --show to print the stored hash, --clear to remove the attestation. Available since v2.37.0.
Starte Manus-artige Dateiplanung. Erstelle task_plan.md, findings.md, progress.md für komplexe Aufgaben.
Iniciar planificación de archivos estilo Manus. Crear task_plan.md, findings.md, progress.md para tareas complejas.
Bridge Claude Code's /goal to the active plan. Derives a goal condition from task_plan.md and invokes /goal so Claude keeps working until the plan is complete. Available since v2.38.0.
启动 Manus 风格的文件规划。为复杂任务创建 task_plan.md、findings.md、progress.md。