status
The `/status` command reads `task_plan.md` from the project directory and displays a compact overview of planning progress, including the current phase with a percentage complete, each phase with status icons (⏸️ for pending, 🔄 for in-progress, ✅ for complete, ❌ for failed), existence of related planning files, and a count of logged errors. Use this command to quickly check project status without reviewing full planning documentation.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/OthmanAdi/planning-with-files/HEAD/commands/status.md -o ~/.claude/commands/status.mdstatus.md
Read task_plan.md from the current project directory and display a compact status summary.
## What to Show
1. **Current Phase**: Extract from "## Current Phase" section
2. **Phase Progress**: Count phases and their status (pending/in_progress/complete)
3. **Phase List**: Show each phase with status icon
4. **Errors**: Count entries in "## Errors Encountered" table if present
5. **Files Check**: Confirm which planning files exist
## Status Icons
- `[ ]` or "pending" → ⏸️
- "in_progress" → 🔄
- `[x]` or "complete" → ✅
- "failed" or "blocked" → ❌
## Output Format
```
📋 Planning Status
Current: Phase {N} of {total} ({percent}%)
Status: {status_icon} {status_text}
{icon} Phase 1: {name}
{icon} Phase 2: {name} ← you are here
{icon} Phase 3: {name}
...
Files: task_plan.md {✓|✗} | findings.md {✓|✗} | progress.md {✓|✗}
Errors logged: {count}
```
## If No Planning Files Exist
```
📋 No planning files found
Run /plan to start a new planning session.
```
## Keep It Brief
This is a quick status check, not a full report. Show just enough to answer "where am I?" without re-reading all the files.Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.
Persistent file-based planning for multi-step AI-agent work. Keeps task_plan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and emits aggregate counts only; --replay may emit bounded nonce-framed excerpts. Optional gated mode can request continuation only when the host supports it and never runs commands declared in Markdown. The skill has no network upload path. Use for research or work needing 5+ tool calls.
بدء تخطيط الملفات بنمط 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.
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.