cf-status

CLI Usage: When unsure about a CLI's interface or flags, run it with --help first. Do NOT attempt to discover functionality by reading plugin source code — doing so leads to incorrect execution from assumptions made without context of the holistic flow.

CLEAR Status

Reads CLEAR state files and displays a formatted summary of the current session, token usage, active workpackage, and context health. Provides token threshold warnings to guide session lifecycle decisions.

---

When to Use This Skill

Load this skill when the user request matches ANY of these patterns:

Trigger Pattern	Example User Request
Asking for session status	"Show me the current session status"
Checking token usage or consumption	"How much of my token budget have I used?"
Verifying context health or loaded state	"Is all the required context loaded?"
General CLEAR status inquiry	"What's the CLEAR status?"

DO NOT use for:

• Initializing CLEAR in a project (use /cf-init instead)
• Reloading or syncing context (use /cf-reload instead)
• Debugging hook or plugin issues (use /cf-debug instead)

---

Usage

/cf-status -- No arguments required. Reads state from .clear/ in the current project.

---

Instructions

Step 1: Pre-flight Check

Verify CLEAR is initialized by checking for .clear/config/clear-manifest.yaml.

if [ -f ".clear/config/clear-manifest.yaml" ]; then
  echo "INITIALIZED"
else
  echo "NOT_INITIALIZED"
fi

If NOT initialized, display: "CLEAR is not initialized in this project. Run /cf-init to set up CLEAR." and stop.

Step 2: Read State Files and Display Output

Read .clear/state/session.json for session data (clearSessionNumber, sessionId, startTime, tokenUsage.*). Read .clear/state/sync-state.json (optional) for active work context (workpackage.displayId, workpackage.title, plan.activePhaseDisplayId). Note: PlanSummary in sync-state has no name field by design — plan identity is carried by master-plan.yaml; the sync summary tracks active phase + progress + blockers only.