- name
SKILL.md
スキルファイルは公開元のリポジトリに置かれたままです。
コピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add coreyhaines31/makerskills --skill project-manager -a cursor -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add coreyhaines31/makerskills --skill project-manager -a claude-code -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add coreyhaines31/makerskills --skill project-manager -a codex -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add coreyhaines31/makerskills --skill project-manager -a grok -yコピーしたメッセージを Grok Bot のチャットで送信してください。Bot がこの SKILL.md を GitHub から取得し、すべての Bot が共有するスキルに追加します。
Install this skill: https://github.com/coreyhaines31/makerskills/tree/HEAD/skills/project-manager公開元より
Methodology-first project management. Kanban + Eisenhower + async. One board per business. Tool-agnostic via adapters.
Each business gets its own kanban with 5 columns:
Backlog → Ready → In Progress → Review/Blocked → Done/Archived
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.
Parse the invocation:
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 's review") instead of generic.
If the business has no mapping yet, jump to setup automatically — ask which tool, save the mapping, return to the requested mode.
Read the relevant section of references/adapters.md for the tool. Each adapter section explains how to:
Adapters use:
$NOTION_API_KEY (already in zshenv). Database with Status select property.gh CLI (already authed). gh project item-list, gh project item-edit.$PLANE_API_KEY and workspace slug).${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./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.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.
Friday pulse + planning:
Default WIP per column (override in your local boards.md per business):
If WIP exceeded in next mode, don't pull more — recommend finishing or moving something to Review/Blocked first.
When generating status / weekly outputs:
decide — when a project hits a real decision, route to /decidedeep-research — when a card needs research before it's actionablebusiness-brainstorm — when an idea on the Backlog deserves pressure-testing before triagejab-hook — when status / shipped items become BIP-post materialproject_*.md) — for portfolio context per businessboards.md per business if truly needed). If the cap is hit, don't pull more — recommend finishing or moving something to Review/Blocked.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-agno
---name: project-managerdescription: When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban…---# skills/project-manager/SKILL.md概要
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).
よくある質問
公開元から skills/project-manager/SKILL.md をダウンロードするか、パスをコピーしてリポジトリを開いてください。PlugMCP はスキルを掲載するだけで、ファイルはホストしていません。
公開元は https://github.com/coreyhaines31/makerskills で管理しています。
Claude、Cursor、Codex、Grok Build は、公開元のリポジトリから追加した SKILL.md を読み込めます。Grok Bot は、チャットでスキルの GitHub フォルダーのリンクを送るとインストールします。