Agent skill · operations · alirezarezvani

pm-skills

Router for project-management skills: sprints, portfolio health, Jira, Confluence, stakeholder comms, plus a delivery loop. Use whenever a delivery request is unclear about which PM skill fits, or the user asks to run a delivery loop or pull Jira data into one.

Why this skill is useful

Adds a comprehensive delivery loop with executable scripts for Jira integration and project management analytics that the AI cannot generate on its own.

What it needs

Requires python3 installed locally. Requires atlassian account access. About 5k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.

What this skill does

Project Management — Domain Orchestrator & Delivery Loop This orchestrator does two jobs. Routing: fork context, classify a PM inquiry with scripts/pmgoalrouter.py, run exactly one of the 8 sub-skills, return a digest. Looping: turn a delivery goal into a bounded agentic loop — pull live Jira data via the bundled Atlassian MCP, bridge it into the domain's deterministic analytics tools, verify every step with machine-run gates, and refuse to close until everything is verified or a human waives it. The bundled .mcp.json wires the Atlassian Remote MCP (https://mcp.atlassian.com/v1/sse, OAuth handled by Claude Code). When to invoke Symptom Sub-skill --- --- "Project/portfolio health, risk EMV, capacity" senior-pm "Sprint velocity, retro follow-through, ceremony health, when-will-it-be-done" scrum-master "JQL, Jira workflows, boards, automation" jira-expert "Confluence spaces, page trees, content audits" confluence-expert "Users, groups, permissions, SSO" atlassian-admin "Reusable Jira/Confluence templates" atlassian-templates "Meeting transcripts, talk time, action items" meeting-analyzer "Status updates, 3P updates, stakeholder comms" team-communications Routing logic (deterministic) Run the router — do not eyeball the table when a script can decide: Exit 0 → routeto names the sub-skill: load its SKILL.md and follow its workflow. Exit 2 → ask ONE clarifying question naming the listed candidates, with a recommended answer. Exit 3 → no signal: ask the user to restate the goal with the deliverable named. Never guess silently; never silently chain a second sub-skill — digest first, confirm, then chain. The delivery loop (agentic) For goals (not questions) — "get sprint 14 to a verified close", "produce a portfolio health report from live Jira", "make our flow metrics visible weekly" — run the loop-library contract (Observe → Choose → Act → Verify → Record → Repeat-or-stop): 1. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills alirezarezvani/pm-skills--9434a3

View the source on GitHub

Browse the @skills marketplace