Pm
When you want to manage projects across your businesses using a kanban + Eisenhower...
Install
npx skills add coreyhaines31/makerskills --skill pm -g -a claude-code -y- Repository
- coreyhaines31/makerskills880
- Category
- AI and agents
- Updated
- 9d ago
- License
- MIT
- Context cost
- Mediumabout 2,006 tokens
- Runs scripts
- No, instructions only
What it does
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 column), weekly (Friday pulse + week planning). Triggers on "/pm," "/pm setup," "/pm triage," "/pm next," "/pm status," "/pm unblock," "/pm weekly," "what should I work on next," "kanban status," "Eisenhower this," "triage my backlog," "what's blocked.
/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 named business (or ask) |
/pm next [business] | next | the named business |
/pm next | next | across all boards (cross-portfolio) |
/pm status [business] | status | the named business (or ask) |
/pm unblock [business] | unblock | the named business (or ask) |
/pm weekly | weekly | all boards (Friday pulse) |
/pm weekly [business] | weekly | the named business |
Step 2, Load board config + personal overlay
Read ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/pm/boards.md (personal, real business list + tool mapping per business). Falls back to references/boards.md in the repo if the local file doesn't exist yet, that's a template.
