Skip to content

coreyhaines31/makerskills / skills/project-manager

project-manager

Verified

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

FileKindSize
SKILL.mdskill md9.5 KB
references/adapters.mdmarkdown5.9 KB
references/boards.mdmarkdown1.1 KB
references/methodology.mdmarkdown5.1 KB

references/methodology.md

View on GitHub
# Methodology — kanban + Eisenhower + async

## Kanban core

### Why kanban

- **Make work visible.** Cards on columns. Nothing hidden in someone's head.
- **Pull, don't push.** Only start new work when capacity opens — finishing > starting.
- **Limit WIP.** Multitasking is the most reliable way to ship nothing. Cap In Progress.
- **Flow over batch.** Small cards moving steadily beats heroic sprints.
- **Inspect and adapt.** Look at flow weekly. If cards pile up in one column, that's the constraint.

### The 5-column flow (the user's default)

```
Backlog  →  Ready  →  In Progress  →  Review/Blocked  →  Done/Archived
```

- **Backlog**: everything that *might* matter. Wide net. No commitment yet.
- **Ready**: triaged. Well-defined enough that anyone could pick it up. Has acceptance criteria.
- **In Progress**: actively being worked. Strict WIP limit.
- **Review/Blocked**: waiting on someone or something external. Should be the shortest-lived state — if a card lives here >5 days, escalate or kill.
- **Done/Archived**: shipped or explicitly killed. Archived weekly.

### Card hygiene

A good card has:
- **Title** — verb-first ("Ship waitlist email" not "Waitlist email")
- **Acceptance criteria** — what does "done" look like? 1–3 bullets.
- **Owner** — even for solo projects: which "hat" is wearing this?
- **Size** — XS / S / M / L (XS = <2 hrs, S = <1 day, M = 2–3 days, L = >1 week — break it down)

Cards that don't meet hygiene live in Backlog, not Ready.

## Eisenhower matrix — the prioritization overlay

```
                    Urgent          Not Urgent
Important           Q1: Do          Q2: Schedule
Not Important       Q3: Delegate    Q4: Delete
```

### Quadrant rules

- **Q1 — Urgent + Important.** Do it. Move to Ready (or In Progress if capacity). These earn priority within Ready.
- **Q2 — Important, Not Urgent.** *This is where leverage lives.* Schedule it. Most Q2 items become Q1 emergencies if neglected — proactively pulling Q2 is the difference between operators who compound and ones who firefight.
- **Q3 — Urgent, Not Important.** Delegate. If there's nobody to delegate to (solo project), ask: is this actually important and I'm mislabeling it, or is it actually noise I'm letting trick me?
- **Q4 — Not Urgent, Not Important.** Archive. The hardest skill in PM is closing tabs.

### When to apply Eisenhower

1. **During Backlog triage** — sort Backlog into Q1/Q2/Q3/Q4; Q1+Q2 candidates move to Ready, Q3 gets delegated or noted, Q4 gets archived.
2. **When picking next from Ready** — within Ready, Q1 > Q2 > Q3.
3. **During weekly planning** — bias next week's pull toward Q2 (preventative + high-leverage).

### Common Eisenhower mistakes

- **Mislabeling Q3 as Q1.** "Urgent" feels urgent because someone else made it urgent. Test: would this matter if you didn't do it for a week?
- **Q4 sneaking into Ready as "easy wins."** If it's not important, the only thing easy about it is the time it takes from Q2 work.
- **Endless Q2.** Q2 is great in moderation. Too many Q2 cards in Ready = the board is wishful thinking, not a commitment. Cap Q2 cards in Ready at ~5 per board.

## Async-first

You're likely running multiple businesses with partners and async clients. Async-first PM means:

1. **Status visible without you.** Anyone should be able to look at the board and know where things stand. No "let me catch you up" calls.
2. **Decisions documented.** When a card moves between columns, the why is in the card or a comment. Compose with `/decide` for big calls.
3. **Cards read like messages.** Title = headline. Body = what a colleague would need to pick this up cold. No "see Slack thread" — link the thread *and* summarize.
4. **Status updates are written, not spoken.** Use the `/project-manager status` output format. Send a Slack message. Don't call.
5. **Reduce back-and-forth.** Every card has owner + acceptance criteria so reviewers don't ping you to ask "what should I check for."

## Cross-portfolio prioritization

When you have N businesses each with their own kanban, the meta-decision is "which board should I work in today?"

Heuristics, in order:

1. **Q1 across all boards first.** Even a Q2 on a hot business loses to a Q1 on a quieter one.
2. **Then: revenue or strategic lever.** Among Q2 items across boards, pull from the business with the most leverage right now.
3. **Then: momentum tax.** If a business has gone 14+ days without progress, prioritize ANY card there. Drift kills compound businesses faster than slow execution.
4. **Then: energy fit.** If two cards are tied, pick the one that matches your current state. Morning analytical brain ≠ end-of-day creative brain.

## WIP limits — recommended defaults

Per business board (override per business in `boards.md`):

| Column | Default WIP |
|---|---|
| In Progress | **3** (max) |
| Review/Blocked | no cap, but flag at 5+ |
| Ready | soft cap at 10 — more than that means you're hoarding, not committing |

Cross-portfolio: across all businesses, **don't exceed 5 In-Progress total**. Each business burns context-switch tax; more than 5 means you're not really In Progress anywhere.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall