pm

# /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...