agentleFS
Sign inStart free
hunterg325hunterg325/claude-code-pm/skills/pm-stop/SKILL.md

pm-stop

Skill2 starsChanged 8 months agoMITView on GitHub

Stop the PM orchestration loop and optionally shut down workers. Use when: user runs /pm:stop, wants to 'stop the PM', 'shut down workers', or 'halt orchestration'.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .claude/pm-state.json for active state

    line 15
  2. Distinctive:

    Wait up to 30 seconds for workers to acknowledge (responses arrive as <channel> events)

    line 21
  3. Distinctive:

    Ask user: "Would you like to clean up orphaned worktrees?

    line 32
  4. Distinctive:

    Remove unmerged worktrees with confirmation for each

    line 37

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/pm:stop — Graceful Shutdown

Shutdown Sequence

  1. Read .claude/pm-state.json for active state
  2. For each active worker:
    • Send abort message via claude-peers: { "type": "abort", "task_id": "{id}", "reason": "PM shutting down" }
    • Log the abort
  3. For each active VO agent:
    • Send abort message
  4. Wait up to 30 seconds for workers to acknowledge (responses arrive as <channel> events)
  5. Update pm-state.json:
    • Move active workers to a shutdown_pending state
    • Record shutdown timestamp
  6. Report summary:
    • Workers notified: N
    • Workers acknowledged: N
    • Tasks that were in progress (may need re-queue on next /pm:start)

Optional Cleanup

Ask user: "Would you like to clean up orphaned worktrees? This removes worktrees for tasks that haven't been merged."

If yes:

  • Run git worktree list
  • Cross-reference with merged branches
  • Remove unmerged worktrees with confirmation for each

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free