pm

Orchestrate multi-step project execution across fleet members with review loops.

65|10|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Apra-Labs/apra-fleet --skill pm-apra-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm
Source: https://github.com/Apra-Labs/apra-fleet/tree/main/skills/pm
Command: npx skills add https://github.com/Apra-Labs/apra-fleet --skill pm-apra-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning a goal into a coordinated, multi-step build-and-review workflow across multiple fleet members, with clear checkpoints and recovery.

Core Features & Use Cases

  • Plan and sprint orchestration: Break work into phased tasks, assign doer/reviewer pairs, and drive execution until completion without the PM writing code directly.
  • Progress tracking with Beads: Maintain a persistent cross-project task graph (epics, tasks, dependencies, verify checkpoints) and prevent duplicate dispatch.
  • Quality gates and review loops: Enforce doer/reviewer cycles, verification checkpoints, backlog handling for deferred findings, and final PR raising.
  • Deployment execution: Run and verify a deployment runbook by preparing deploy.md and executing each step on the target member.

Quick Start

Use the pm skill to create a new sprint and run it end-to-end by issuing: /pm init <project> then /pm plan <requirement> and /pm start <member>.

Frequently Asked Questions about pm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multi-agent project execution across fleet members?

Multi-agent project execution is coordinated by planning phased tasks, dispatching doer/reviewer pairs, tracking persistent task state, and managing review loops to drive sprints to completion. The PM skill orchestrates this workflow without writing code directly.

What is a doer/reviewer review loop for code review workflows?

A doer/reviewer review loop enforces quality gates by assigning one agent to execute code and another to review it. This cycle includes verification checkpoints, backlog handling for deferred findings, and final PR raising to guarantee CI verification without merging.

How do I initialize a sprint and run it end-to-end?

To initialize a sprint end-to-end, issue /pm init <project> to set up the project, then /pm plan <requirement> to generate a phased plan, and finally /pm start <member> to dispatch execution tasks to fleet members.

Do I need a working fleet skill dependency for agent orchestration?

Yes, agent orchestration requires a working fleet skill dependency to dispatch and manage fleet members. The PM skill relies on this fleet infrastructure and uses Beads for lifecycle integrity to maintain persistent cross-project task graphs.

Can I execute a deployment runbook after a reviewed PR is raised?

Yes, deployment runbook execution is supported by preparing a deploy.md file and executing each step on the target fleet member. This happens after the doer/reviewer review loop and PR verification are complete, ensuring safe deployments.

Why does the PM skill enforce doer-only code execution?

Doer-only code execution is enforced to maintain strict separation of duties within the review loop. By preventing the PM agent from writing code directly, the system guarantees that all code changes pass through verification checkpoints and reviewer approval before PRs are raised.