SkillAgentSearch skills...

project-manager

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).

Install / Use

npx skills add coreyhaines31/makerskills --skill project-manager

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Our assessment of project-manager

project-manager scores 89/100 on our quality scale, 29th of 83 Project & Program Management skills we index (top 35%).

Its SKILL.md is 9.4 KB long, well organised into 17 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.

It has 824 GitHub stars, a meaningful sign that others use it.

Substance
29/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 25 days ago, so project-manager is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

project-manager compared with similar skills

All 4 of these similar skills score higher than project-manager; compare them before choosing.

SkillScoreStarsUpdatedFormat
project-manager (this skill)by coreyhaines318982425d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install project-manager?
Run npx skills add coreyhaines31/makerskills --skill project-manager. The install tabs above show the steps for each supported agent.
Which AI agents does project-manager work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is project-manager safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is project-manager still maintained?
The repository was last updated 25 days ago, so project-manager is actively maintained.

name: project-manager description: 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 "/project-manager," "/pm," "/pm setup," "/pm triage," "/pm next," "/pm status," "/pm unblock," "/pm weekly," "project manager," "what should I work on next," "kanban status," "Eisenhower this," "triage my backlog," "what's blocked." Not for specing or launch-readiness checks on an app (see product-manager). metadata: version: 0.2.0

/project-manager — 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 | |---|---|---| | /project-manager setup [business] | setup | the named business | | /project-manager triage [business] | triage | the named business (or ask) | | /project-manager next [business] | next | the named business | | /project-manager next | next | across all boards (cross-portfolio) | | /project-manager status [business] | status | the named business (or ask) | | /project-manager unblock [business] | unblock | the named business (or ask) | | /project-manager weekly | weekly | all boards (Friday pulse) | | /project-manager weekly [business] | weekly | the named business |

Step 2 — Load board config + personal overlay

Read ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/project-manager/boards.md (personal — real business list + tool mapping per business). If that directory doesn't exist but ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/pm/ does (the skill was called pm before v0.2.0), read from pm/ instead and offer once to move it: mv "${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/pm" "${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/project-manager". Never move it without a yes. Falls back to references/boards.md in the repo if the local file doesn't exist yet — that's a template.

Also try to load ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/project-manager/team.local.md if present — this is where the user lists partners, active clients, and typical blocker phrasings. Use it to make status output specific ("Waiting on <partner>'s review") instead of generic.

| Field | Example | |---|---| | business | <slug> | | tool | notion / github / plane / linear / obsidian / manual | | board_id or URL | tool-specific | | column overrides | only if this board doesn't use the default 5 columns |

If the business has no mapping yet, jump to setup automatically — ask which tool, save the mapping, return to the requested mode.

Step 3 — Load the adapter

Read the relevant section of references/adapters.md for the tool. Each adapter section explains how to:

  • List cards / issues / pages by column
  • Read a single card's full content
  • Create a card
  • Move a card between columns
  • Add a comment / note

Adapters use:

  • Notion → $NOTION_API_KEY (already in zshenv). Database with Status select property.
  • GitHub Projects → gh CLI (already authed). gh project item-list, gh project item-edit.
  • Plane → Plane API (needs $PLANE_API_KEY and workspace slug).
  • Linear → Linear MCP or API key.
  • Obsidian → local kanban markdown files in the vault. Read/write directly.
  • Manual → ask the user to paste the current board state; offer to write back to a local markdown file.

Step 4 — Run the mode

setup

  • Ask which tool the business uses
  • Walk through column setup (default 5 columns; offer custom)
  • Save mapping to ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/project-manager/boards.md (NOT to references/boards.md in the repo — that's a template only). Create the parent directory if it doesn't exist yet.
  • Optionally seed the board with starter cards from a conversation about what's on the user's mind for that business

triage

  • Pull the Backlog column
  • Apply Eisenhower (Q1/Q2/Q3/Q4) — show the user the matrix view
  • Recommend moves:
    • Q1 (urgent + important) → move to Ready or In Progress now
    • Q2 (important, not urgent) → move to Ready, schedule when
    • Q3 (urgent, not important) → delegate (to whom?) or move to Ready if no one
    • Q4 (neither) → archive
  • Apply moves via the adapter (or output text the user applies manually)

next

  • Single board: pull Ready, then In Progress. If WIP exceeded, surface what to finish first. If WIP available, recommend top Ready item by Eisenhower priority.
  • Cross-portfolio (/project-manager next with no business): pull Ready from every board, Eisenhower-rank, recommend top 1–3 across all businesses. Bias toward Q1 then Q2.

status

Generate an async-shareable snapshot:

# [Business] — Status as of YYYY-MM-DD

**Shipped this week:** N cards
- <card title>
- <card title>

**In progress:** N cards
- <card title> — <who/what>

**Review/Blocked:** N cards
- <card title> — blocked on <reason>

**Up next:** top 2–3 from Ready
- <card title>
- <card title>

**Open question:** <one thing that would unblock progress if answered>

Output is paste-ready for Slack, Notion, email, partner DM.

unblock

  • Read everything in Review/Blocked
  • For each card: surface the blocker, suggest an action (nudge X, escalate to Y, descope, kill, move back to In Progress if blocker is gone)
  • Output a short list of moves

weekly

Friday pulse + planning:

  1. For each board: shipped this week, in progress, blocked
  2. Cross-portfolio: where's momentum? where's drift?
  3. Plan next week: 3–5 Q2 items to pull from Ready into In Progress on Monday
  4. Output the combined snapshot — pasteable into Notion weekly log, partner update, or personal journal

WIP limits

Default WIP per column (override in your local boards.md per business):

| Column | Default WIP | |---|---| | In Progress | 3 | | Review/Blocked | (no limit — but flag if >5) |

If WIP exceeded in next mode, don't pull more — recommend finishing or moving something to Review/Blocked first.

Async-first writing rules

When generating status / weekly outputs:

  • Lead with the headline — what shipped this week, or what's at risk
  • Be specific — "shipped X" not "made progress on Y"
  • No verbs without subjects — write so the reader can pick up cold
  • Blockers name the blocker — "waiting on designer's review" not "blocked"
  • Open questions are explicit — one bolded line per status that asks for what would unblock momentum

Composes with

  • decide — when a project hits a real decision, route to /decide
  • deep-research — when a card needs research before it's actionable
  • business-brainstorm — when an idea on the Backlog deserves pressure-testing before triage
  • jab-hook — when status / shipped items become BIP-post material
  • Memory (project_*.md) — for portfolio context per business

Notes on quality

  • Limit WIP. Multitasking is the most reliable way to ship nothing. Cap In Progress at 3 (override in your local boards.md per business if truly needed). If the cap is hit, don't pull more — recommend finishing or moving something to Review/Blocked.
  • Lead with the headline in every status output — what shipped this week, or what's at risk. Not "made progress on X" — that's noise.
  • Be specific. "Shipped the primary logo variant" beats "made progress on branding." Specificity signals real motion; vagueness signals none.
  • No verbs without subjects. Write status so the reader can pick up cold — 3 weeks later or forwarded to a partner who missed the last update.
  • Blockers name the blocker. "Waiting on designer's review of the homepage draft" — not "blocked." Blockers without names create no urgency.
  • Open questions are explicit — one bolded line per status that asks for what would unblock momentum. Async momentum lives or dies on how well open questions are surfaced.
  • Tool-agnostic by design. project-manager speaks Kanban + Eisenhower; the adapters (Notion / GitHub / Plane / Linear / Obsidian / manual) translate. Adding a new tool = one adapter file, not a rewrite.

Related Skills

View on GitHub
GitHub Stars824
CategoryProject
Updated25d ago
Forks67

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions