project-management

20 slash commands organized by project lifecycle stage.

Analyze sprint or project burndown and forecast completion

Draft a formal change request with impact analysis

Define stakeholder communication cadence, channels, and ownership

Record and track project decisions with context and rationale

Map and track cross-team or cross-project dependencies

Run a multi-dimensional project health assessment — triggers the orchestrator

Generate a kickoff meeting agenda and preparation checklist

Compile lessons learned into a structured knowledge document

Define project scope, objectives, stakeholders, and success criteria

Generate a project closeout report with handoff checklist

Plan team allocation, roles, and capacity

Facilitate a retrospective in multiple formats

Create a risk register with identification, scoring, and mitigation strategies

Review and update the project risk register

Build a project schedule with milestones and dependencies

Plan a sprint or iteration with scope, capacity, and commitments

Map stakeholders by influence and interest with engagement strategies

Generate daily standup summaries or async standup templates

Generate a project status report in RAG format

Create a work breakdown structure for a project

**File:** [`orchestrator.md`](./orchestrator.md)

The Orchestrator is the master routing agent for multi-stage project management workflows. When a user presents a request that spans lifecycle stages — health checks, new project setup, project recovery, closeout — the Orchestrator classifies the request, selects the right skills, sequences them, and synthesizes their outputs into a unified report.

Retrospectives, lessons learned, and project closeout for software and general PMs Use when user asks to "run a retrospective", "close out the project", "lessons learned", or mentions post-mortem, project handoff, or release notes.

Standups, sprint planning, decision tracking, and change management for software and general PMs Use when user asks to "plan a sprint", "run standup", "track decisions", or mentions sprint planning, daily standup, change requests, or kanban.

Project charters, stakeholder mapping, and kickoff planning for software and general PMs Use when user asks to "create a project charter", "map stakeholders", "kick off a project", or mentions project setup, stakeholder analysis, or kickoff meeting.

Status reporting, burndown analysis, risk reviews, dependency tracking, and project health checks for software and general PMs Use when user asks to "write a status report", "check project health", "track progress", or mentions burndown, RAG status, risk review, or earned value.

WBS, scheduling, resource planning, risk management, and communication planning for software and general PMs Use when user asks to "create a WBS", "build a project schedule", "risk register", or mentions work breakdown structure, resource planning, RACI, or critical path.