pm-status
Skill2 starsChanged 8 months agoMITView on GitHub
Show PM orchestration status. Use when: user runs /pm:status, asks 'what's the PM doing', 'show workers', 'task queue status', or wants to see active workers and task queue.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ridwankustanto/mandortheir own version, first seen Oct 11, 2026
- pinkroosterai/PinkRoosterMcptheir own version, first seen Mar 18, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- pinkroosterai/PinkRoosterMcp★ 2same name
- ridwankustanto/mandor★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read .claude/pm-state.json and reconcile with live list_peers data.
- Very specific: line 39
If pm-state.json doesn't exist, report "PM is not running.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/pm:status — Show PM Status
Read .claude/pm-state.json and reconcile with live list_peers data. Display:
Output Format
Active Workers
| Task | Worker | Branch | Status | Duration |
| For each entry in active_workers, show task_id, peer_id, branch, status, and time since spawned_at. |
Verification Officers
| Task | VO | Status | PR | Review Loops |
| For each entry in vo_agents, show task_id, vo_peer_id, status, pr_url, review_loop_count. |
Queued Tasks
Numbered list of queued_tasks with task_id, title, priority.
Recently Completed
Last 5 entries from completed_tasks with task_id, pr_url, completed_at.
Escalations
Any unresolved escalations with task_id, type, message, timestamp.
Health
- PM peer ID and uptime
- Workers: {active}/{max_concurrent} slots used
- Broker: connected/disconnected (based on list_peers success)
If pm-state.json doesn't exist, report "PM is not running. Use /pm:start to launch."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.