pm-skills
Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it be done', 'run the delivery loop'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a full goal→plan→execute→verify→close delivery loop through the repo-wide agent-harness with Jira MCP data bridged into the domain's an
Profile →npx skills add alirezarezvani/claude-skills --skill pm-skills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Project Management — Domain Orchestrator & Delivery Loop This orchestrator does two jobs. **Routing:** fork context, classify a PM inquiry with `scripts/pm_goal_router.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 upd
- When to invoke
- Routing logic (deterministic)
- The delivery loop (agentic)
- Hard rules (agentic delegation governance)
- Forcing-question library (grill-with-docs pattern)
- Assumptions
- Non-goals
- Output artifacts
- Anti-patterns (do not)
- References
python3 scripts/pm_goal_router.py --text "<the goal>" --output json python3 scripts/jira_snapshot_bridge.py --input snapshot.json --to flow # WIP, throughput, cycle time p50/85/95, work-item age, SLE, aging alerts python3 scripts/jira_snapshot_bridge.py --input snapshot.json --to sprint > s.json # scrum-master schema python3 ../scrum-master/scripts/velocity_analyzer.py s.json # velocity + volatility + forecast python3 scripts/delivery_loop_gate.py --plan plan.json --mode plan # exit 2 = blocked python3 scripts/delivery_loop_gate.py --plan plan.json --mode close # exit 4 = close refused python3 engineering/agent-harness/skills/agent-harness/scripts/goal_compiler.py \ python3 engineering/agent-harness/skills/agent-harness/scripts/loop_controller.py init|next|record|verify|close ...
What does the pm-skills skill do?
Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it be done', 'run the delivery loop'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a full goal→plan→execute→verify→close delivery loop through the repo-wide agent-harness with Jira MCP data bridged into the domain's an
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill pm-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.