Status Report

/status gives a full health report across every project in your register. The daily briefing focuses on today, and /status shows the whole picture, including paused and recently archived projects, milestones and your recent sessions. It reads your register and the last seven days of git history, and changes nothing unless you ask it to.

Run a Report

1. Type /status in Claude Code and press Enter to see every project in the register.
2. Add a category, a tag or both after the command when you want a narrower report.
3. Ask for a change in plain words if the report shows something to fix.

Filters

You type	The report shows
/status marketing	Projects in the marketing category only
/status --tag compliance	Projects tagged compliance
/status --tag automation,integration	Projects with any of the listed tags
/status client --tag training	Projects in the client category that also carry the training tag

A filtered report states the filter at the top and applies it to every section, counts included. When nothing matches, the report says so.

What the Report Contains

• Banner and time: the workspace banner and when Claude generated the report.
• Projects by status: a table each for in progress, paused, overdue and archived in the last 30 days. Each project carries a traffic light, and the in-progress table shows milestones as done out of total.
• Projects by category: how many projects that are not archived sit in each category, with their IDs.
• Priorities and pending items: your immediate, weekly and upcoming priorities, and items waiting for a project.
• Recent session activity: up to ten sessions from the session history in your register.
• Warnings: stale projects not worked for more than seven days, and projects past their due date.
• Delivery overview: milestones due in the next 30 days, the last five completed and any overdue. This section appears only when projects have milestones, and it ends with a pointer to /timeline.
• PRIMA health check: whether the product’s critical files match a separate copy of the release files, when one is on your computer.
• Recommended actions: the same ranked list as the daily briefing.

Status and Traffic Lights explains the traffic lights, the sort order and the category icons.

The Health Check

The health check reads the critical list in prima-manifest.json. It compares each critical file in your workspace with the same file in a copy of the PRIMA Project Management release files, using diff -q. A file that matches passes. A file that differs appears with a warning to run the update or confirm the change was intended.

### PRIMA Health
⚠️ Critical file modified: .claude/rules/state-validation.md
   Run the update script to restore the upstream version, or verify the change is intentional.

Note

The check compares your files with a separate copy of the PRIMA Project Management release files. An install from the email you receive when you buy does not keep such a copy, so in most workspaces this section does not appear, and Claude leaves it out without comment.

Changes You Can Ask For

You say	What changes
“complete P012” or “archive P012”	Status becomes archived, stoppedAt and lastAction clear, lastWorked becomes today
“pause P012”	Claude asks for a reason, then sets the status to paused
“resume P012”	Status returns to in-progress, and the pause reason and stoppedAt clear
“add project Client Onboarding”	A new project with the next free ID and status in-progress
“update priorities”	Claude asks for new immediate, weekly and upcoming priorities and records them

Claude backs up your register before each change and validates it afterwards.

Related Pages

• The Daily Briefing gives the short version each morning.
• The Timeline draws the dates from this report on a chart.
• /status in AI Business OS describes the base version this command replaces.