Agent skill · Backend & API

pm

When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian file-based, or manual mode). Async-first output. Six modes — setup (scaffold a new board for a business), triage (Eisenhower-sort the backlog), next (pick the next thing to work on, single board or across all), status (paste-ready async snapshot), unblock (diagnose Review/Blocked co

coreyhaines31github.com/coreyhaines31GitHub ↗
claude-codeMIT
Install
npx skills add coreyhaines31/makerskills --skill pm --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 9 KB
Bundled scripts: none
Version: 0.1.1
Path: skills/pm/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 500

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /pm — Project management across the portfolio Methodology-first project management. Kanban + Eisenhower + async. One board per business. Tool-agnostic via adapters. ## Mental model Each business gets its own kanban with 5 columns: ``` Backlog → Ready → In Progress → Review/Blocked → Done/Archived ``` - **Backlog**: everything that *might* matter — not yet committed - **Ready**: triaged, well-defined, can be picked up - **In Progress**: actively being worked - **Review/Blocked**: waiting on someone else, review, or external dependency - **Done/Archived**: shipped or killed **Eisenhower** sits on top of the board — used to triage Backlog → Ready (which items make the cut) and to pick next from Ready (which Ready item to pull). ``` Urgent Not Urgent Important Q1: Do Q2: Schedule ← Q2 is the high-leverage zone Not Important Q3: Delegate Q4: Delete ``` **Async-first**: every status snapshot should read like a Loom you didn't have to record. Make work visible without requiring a meeting. ## Step 1 — Detect mode and target Parse the invocation: | Invocation | Mode | Target | |---|---|---| | `/pm setup [business]` | setup | the named business | | `/pm triage [business]` | triage | the na

What's inside
Steps it walks through
  1. Mental model
  2. Step 1 — Detect mode and target
  3. Step 2 — Load board config + personal overlay
  4. Step 3 — Load the adapter
  5. Step 4 — Run the mode
  6. setup
  7. triage
  8. next
  9. status
  10. unblock
  11. weekly
  12. WIP limits
  13. Async-first writing rules
  14. Composes with
Ships with 3 files
  • references/adapters.md
  • references/boards.md
  • references/methodology.md
More from makerskills
All skills →
About this skill
What does the pm skill do?

When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian file-based, or manual mode). Async-first output. Six modes — setup (scaffold a new board for a business), triage (Eisenhower-sort the backlog), next (pick the next thing to work on, single board or across all), status (paste-ready async snapshot), unblock (diagnose Review/Blocked co

How do I install it?

Run `npx skills add coreyhaines31/makerskills --skill pm --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 coreyhaines31/makerskills, a repository with 500 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.

Keep going