Command
/plan-loop
Run a planning-aware cadence with Claude Code's /loop. Default tick checks plan status, runs check-complete, nudges progress.md update if stalled. Available since v2.38.0.
One command from planning-with-files.
shell
$ npx -y skills add OthmanAdi/planning-with-files --agent claude-codeShips with planning-with-files. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/plan-loop
Context preview
What this command does when you run it.
Run a planning-aware cadence with Claude Code's /loop. Default tick checks plan status, runs check-complete, nudges progress.md update if stalled. Available since v2.38.0.
Stats
Stars25,655
Forks2,157
LanguagePython
LicenseMIT
Ships with planning-with-files
Command definition
plan-loop.md
--- description: "Run a planning-aware cadence with Claude Code's /loop. Default tick checks plan status, runs check-complete, nudges progress.md update if stalled. Available since v2.38.0." disable-model-invocation: true allowed-tools: "Read Bash" --- 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.
