explaingit

phuryn/pm-brain

Analysis updated 2026-06-24

43PythonAudience · pm founderComplexity · 2/5Setup · easy

TLDR

Markdown-folder second brain for product managers driven by Claude Code, with six slash commands for ingest, prep, review, ideate, risk and plan.

Mindmap

mindmap
  root((pm-brain))
    Inputs
      Notion exports
      Jira CSVs
      Interview notes
      Hunches
    Outputs
      Knowledge files
      Stakeholder briefs
      Risk scans
      Six block plans
    Use Cases
      Run weekly review
      Prep stakeholder meetings
      Capture provenance tagged claims
    Tech Stack
      Markdown
      Claude Code
      Python eval suite
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Run a personal second-brain for product management without any cloud sync

USE CASE 2

Migrate existing Notion exports and Jira CSVs into a single markdown brain

USE CASE 3

Draft a one-page stakeholder brief before a meeting via /prep

USE CASE 4

Do a Friday sweep that drafts the bigger calls across the whole folder

What is it built with?

MarkdownClaude CodePython

How does it compare?

phuryn/pm-brainarccalc/dwmfixlorenliu13/claude-code-for-hydrology
Stars434344
LanguagePythonPythonPython
Setup difficultyeasyeasyeasy
Complexity2/52/52/5
Audiencepm foundergeneralresearcher

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 30min

Two-stage install: a curl-tar of the skill into ~/.claude/skills, then per-folder /pm-brain bootstrap inside Claude Code.

In plain English

PM Brain is a second-brain system for product managers built on plain markdown files in a folder on a laptop. Claude Code reads the files before answering, writes back into them after, and runs a Friday sweep across the whole folder. There is no vector database, no cloud sync, and no embedded agent memory. The author frames it as a research preview: the architecture has months of dogfooding behind it on a content-focused sister project, but real-team PM installs are days old. Install has two stages. First, a one-time install of the skill itself into ~/.claude/skills/pm-brain/, which the README shows via a curl-and-tar one-liner on macOS, Linux, WSL, and Git Bash, plus a PowerShell equivalent for Windows. Second, a per-product bootstrap: cd into the folder you want the brain to live in, run claude, and call /pm-brain. The skill either starts greenfield in an empty folder or absorbs existing PM artifacts like Notion exports and Jira CSVs in migration mode. A short five-batch interview captures the company, role, and current priorities. The brain has one loop. You ingest an artifact, the original goes into source/ untouched and a synthesis lands in ingestion/, the durable layer (knowledge/, hypotheses/, decisions/, stakeholders/) is updated wherever the signal applies, and every claim is tagged with provenance: documented interview, verbal comment, your hunch, or general industry knowledge. Friday's /review reads the whole folder, fixes small drift, and drafts the bigger calls. Six commands drive day-to-day use: /ingest feeds in an artifact, /prep writes a one-page brief before a stakeholder meeting, /review is the weekly sweep, /ideate surfaces three to seven directions with evidence tags, /risk runs a five-area scan, and /plan drafts a six-block plan covering what is known, assumptions, who to interview, hypotheses, experiments, and decision points. The README is explicit about what PM Brain is not: not a notes app, not a chatbot with memory, not a vector database, not an agent memory system, and not autonomous product management. Judgment stays with the human, the brain only stores what the user and agent deliberately wrote down. The eval suite reports 404 of 406 checks passing across 17 synthetic PM scenarios, roughly 99.5 percent, with all 329 structural checks green and 75 of 77 LLM-judge content checks passing.

Copy-paste prompts

Prompt 1
Install pm-brain into ~/.claude/skills/pm-brain and bootstrap a new brain folder for my product.
Prompt 2
Use /ingest in pm-brain to absorb this Notion export and update the knowledge and decisions layers.
Prompt 3
Run /prep in pm-brain to draft a one-page brief for tomorrow's exec stakeholder meeting on pricing.
Prompt 4
Run /risk in pm-brain across my current roadmap folder and surface the top five concerns.
Prompt 5
Adapt pm-brain's provenance tagging convention for a separate research notes folder.

Frequently asked questions

What is pm-brain?

Markdown-folder second brain for product managers driven by Claude Code, with six slash commands for ingest, prep, review, ideate, risk and plan.

What language is pm-brain written in?

Mainly Python. The stack also includes Markdown, Claude Code, Python.

How hard is pm-brain to set up?

Setup difficulty is rated easy, with roughly 30min to a first successful run.

Who is pm-brain for?

Mainly pm founder.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.