Skip to main content
command CX Codex

status · othmanadi — Claude Code command: what it does, how to install

Displays current task phases, completion percentage, and errors from task_plan.md. Runs when you need a quick status check without loading companion files into context.

MIT ★ 28,179 updated 2026-11-04

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add OthmanAdi/planning-with-files
/plugin install planning-with-files@planning-with-files
Open on GitHub

What status does

The command resolves the target plan directory using resolve-plan-dir.sh or its PowerShell counterpart. It respects PWF_PLAN_ROOT as the project root and relies on PLAN_ID when multiple tasks exist. If multiple plans are detected without a selector, the script prints PWF_PLAN_AMBIGUOUS_V1 and refuses to guess, requiring an explicit slug.

Execution stays lightweight because it only parses task_plan.md. It confirms whether findings.md and progress.md exist on disk without reading their contents. The output lists phase progress, visual indicators for each milestone, and a count of entries in the logged errors table.

What it helps with

  • check the current phase and progress percentage without loading all files
  • verify whether task_plan.md, findings.md, and progress.md exist on disk
  • count logged entries in the errors table
  • identify the active plan using PWF_PLAN_ROOT and PLAN_ID

Example prompts for the agent

  • /planning-with-files:status
  • Show current plan status and check companion files
  • PLAN_ID=migration-step show progress across all phases

How to install status

1Plugin marketplace

/plugin marketplace add OthmanAdi/planning-with-files
/plugin install planning-with-files@planning-with-files

2Manually: put the files in place

.claude/commands/planning-with-files-status.md

The built-in /status overrides a file with the same name, so the file is renamed. Call it with /planning-with-files-status. For all projects use ~/.claude/commands/

Questions about status

How do I install status in Claude Code?

Run /plugin marketplace add OthmanAdi/planning-with-files, then run /plugin install planning-with-files@planning-with-files. Alternatively, add .claude/commands/planning-with-files-status.md directly.

What does status do?

It prints a compact summary showing the active phase, total progress percentage, a phase list with status icons, and the error count. It also checks whether companion Markdown files exist.

How does status handle multiple active plans?

When ambiguous plans exist without a selector, resolve-plan-dir.sh outputs PWF_PLAN_AMBIGUOUS_V1. The command stops and prompts you to specify PLAN_ID=<slug> instead of choosing one automatically.

Source text

status.md · MIT
---
description: "Show current planning status at a glance - phases, progress, and any logged errors."
---

Resolve the selected task, then read `task_plan.md` from that one directory and display a compact status summary.

## Resolve the Selected Task

Validate `PWF_PLAN_ROOT` as an absolute existing project root when set; refuse an invalid root pin. Otherwise use cwd as the project root. Run `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. Read only its `task_plan.md`; check whether `findings.md` and `progress.md` exist without loading their contents. A root `task_plan.md` must not override it.
- Empty output with non-empty `PLAN_ID` means the plan selector was rejected. Report that the pin did not resolve and read nothing else.
- Empty output where `resolve-plan-dir.sh --check-ambiguity` (PowerShell: `-CheckAmbiguity`) prints `PWF_PLAN_AMBIGUOUS_V1` means multiple plans exist without a selector. Report that and ask the user to set `PLAN_ID=<slug>`; do not pick one.
- Otherwise empty output is the legacy project-root convention: read `task_plan.md` from the validated project root (`PWF_PLAN_ROOT` when set), if it exists, and check the companion files there. A valid root pin alone does not reject a legacy root plan. If no plan exists, report that without creating one.

`.planning/.active_plan` is a shared default; it does not bind a parallel session.

## 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.

© OthmanAdi · MIT · OthmanAdi/planning-with-files

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

status by other authors comes first.

status Seth Hobson Shows Conductor project status, active tracks, and next actions. Use it to inspect task progress and spot blockers. CX Codex +1 348installs status official Vercel Labs status inspects the state of a linked Vercel project, including recent deployments, domain health, and log drain setup. CX Codex GP ChatGPT +1 348installs status carlrannaberg status evaluates repository state via Git, categorizes modified files by type, and suggests actions before commits or rebases. CX Codex +1 ★ 763repo stars status Son Nguyen Polls the local Claude Code Agent Monitor dashboard to print health status and session counts in a single line. CX Codex +1 ★ 1,198repo stars status OthmanAdi status reads task_plan.md to display phase milestones and summarizes notes from findings.md. CX Codex +1 ★ 540repo stars exec-plan pproenca exec-plan manages self-contained Markdown execution plans across agent sessions for tasks touching more than three files or taking over an hour. CX Codex +1 239installs make-issue-spec pchalasani make-issue-spec generates a markdown task specification and implementation plan in issues/. Adds the file to Git staging if permissions allow. CX Codex +1 ★ 2,039repo stars plan-task NeoLabHQ plan-task turns a rough task spec into a plan with acceptance criteria, an architecture overview and verifiable phases, each gated by a judge. CX Codex +1 1,300installs team-status Seth Hobson team-status shows the members, task state and progress of an active agent team. Useful when several subagents are working on the same project. CX Codex +1 ★ 42,780repo stars notion-spec-to-implementation makenotion The notion-spec-to-implementation Claude Code skill turns Notion specs into implementation plans and linked tasks. It checks delivered work against requirements and records progress. CX Codex +1 389installs Task Breakdown Specialist daffy0208 Task Breakdown Specialist slices heavy development tasks into 2-minute and 15-minute micro-steps with built-in time buffers to lower activation energy and stop procrastination. CX Codex +1 149installs

From the same set14

The whole set →
plan Loads the planning-with-files skill and starts planning in the current project. Handy when you want to begin a new plan or continue an existing one. CX Codex +1 ★ 28,179repo stars plan Starts Manus-style file-based planning for complex engineering workflows. Generates task_plan.md, findings.md, and progress.md or restores an active session. CX Codex +1 ★ 28,179repo stars pwf pwf is a Claude Code command that plans tasks through three project files. The agent invokes it for a request to map out work. CX Codex +1 ★ 28,179repo stars pwf The pwf command sets up the planning-with-files workflow, generating a task plan, findings log and progress file for the current project. CX Codex +1 ★ 28,179repo stars plan-doctor The plan-doctor command for Claude Code checks planning-with-files plan lookup, injection, and attestation. Run it when hooks go silent or on a new machine. CX Codex +1 ★ 28,179repo stars plan-goal plan-goal builds a completion condition out of task_plan.md and feeds it to /goal, so the agent keeps moving through the whole plan. CX Codex +1 ★ 28,179repo stars plan-attest plan-attest locks the active task_plan.md file using a SHA-256 hash. Built-in hooks prevent plan injection into model prompts whenever the file content diverges from the attested hash. CX Codex +1 ★ 28,179repo stars plan-loop plan-loop — a planning-aware slash command runs recurring /loop checks against your plan files. Use it when phased work needs a regular progress tick. CX Codex +1 ★ 28,179repo stars

Project sponsors

Companies that keep this analytics open