/prep
Surface what to ask, raise, or watch for in an upcoming conversation.
$ npx -y skills add phuryn/pm-brain --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/prep
Context preview
What this command does when you run it.
Surface what to ask, raise, or watch for in an upcoming conversation.
Command definition
prep.md/prep
Surface what to ask, raise, or watch for in an upcoming conversation.
Input
Stakeholder slug (`/prep acme-ops`), meeting name (`/prep weekly-exec-review`), or meeting type (`/prep 1:1`). If multi-attendee, pass the slug list or the meeting name.
Loads
- `stakeholders/<slug>.md` for each attendee
- `decisions/` filtered to ones affecting them or the topic
- Active `hypotheses/<slug>.md` they care about or own
- Last 3 `ingestion/meetings/<slug>-*.md` with this person or this meeting type
- `knowledge/strategy.md § Tensions` if any tension intersects their concerns
Updates
Nothing at call time. `/prep` is read-only. After the meeting, run `/ingest` on the notes.
Surfaces
- Their open asks and last unresolved concern (with date)
- Decisions made since last touch that affect them
- Active hypotheses where their judgment matters
- One sentence on what changed in their world since last 1:1
- 3-5 suggested questions or talking points
- One flag if `Last touched` is older than 3 weeks for a high-influence stakeholder
A second brain for product managers. Plain markdown files in a folder on your laptop. Claude reads them before answering, writes to them after, sweeps them every Friday. No vector DB. No cloud. No agent memory tricks. You manage one product.
Repo: phuryn/pm-brain
Other commands on pm-brain.
- /decide
Log a decision. Drafts a complete decision file from the existing evidence trail and surfaces it for PM sign-off.
Open command - /hypothesize
Generate or refresh hypotheses for a feature. Works **pre-ship** (proactive, organized by the 5 risk areas) or **post-ship** (data-derived from analytics / interviews / churn — "why is retention dropping?"). Same schema either way; the `Origin` field distinguishes them.
Open command - /ideate
Generate solution directions for a problem, grounded in what the brain already knows. Not a brainstorm. A synthesis.
Open command - /ingest
Route a new artifact into the brain. Four shapes, one verb.
Open command - /plan
Turn a new team objective into a concrete plan: what we know, what we assume, who to interview, which hypotheses to open, which experiments to run, what decision would unlock execution.
Open command - /review
The weekly maintenance sweep. Six checks. Produces a dated report and edits files directly where confidence is high.
Open command