← ClaudeAtlas

pmlisted

Query and drive the PM role for an initiative on the orchestrator project -- inspect state (what's ready/blocked, dependency graph, initiative status) and trigger the PM's owned actions (decompose a validated spec into a feature graph, recompute dependencies, open feature issues, close a landed initiative). Use when a human wants to ask about or advance an initiative's feature graph.
specfuse/orchestrator · ★ 0 · AI & Automation · score 68
Install: claude install-skill specfuse/orchestrator
<!-- Copyright 2026 Specfuse Contributors Licensed under the Apache License, Version 2.0. See LICENSE. --> Converted from the orchestrator repo's PM role (`agents/pm/CLAUDE.md`, role config v1.6.3); preserves that role's behavior for human-driven, conversational invocation as a plugin skill. Read-and-act router: the human asks in natural language, this skill loads the PM role and routes to the right sub-behavior. The user wants to inspect or advance an initiative's feature graph -- ask a status question, or trigger one of the PM role's owned transitions. ## Process 1. Switch into the **PM agent** role: read this plugin's bundled `agents/pm.md` (role, entry transitions owned, output artifacts, verification, escalation, anti-patterns) before acting. It is the flattened, distributable form of the orchestrator repo's `agents/pm/CLAUDE.md` -- if the two drift, the source under `agents/pm/CLAUDE.md` wins. 2. Read the human's request and route to one of two modes. Ask **one** disambiguating question only if the intent or target initiative is unclear; don't interrogate. **Read / query** (no state change -- answer from direct inspection, never a cached or session-memory view): - Initiative status: current lifecycle state, feature count by state. - What's `ready` / `pending` / `blocked`, and *why* a given feature is blocked (name the unmet `depends_on` target and its actual state). - The dependency graph or a single feature's dependency chain