decide
Log a decision. Drafts a complete decision file from the existing evidence trail and surfaces it for PM sign-off.
Drift check between recent decisions / ingestions / active hypotheses and `knowledge/strategy.md`. Read-only synthesis. Surfaces tensions for the PM to resolve; does NOT silently edit strategy.
$ npx -y skills add phuryn/pm-brain --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/strategy-checkContext preview
What this command does when you run it.
Drift check between recent decisions / ingestions / active hypotheses and `knowledge/strategy.md`. Read-only synthesis. Surfaces tensions for the PM to resolve; does NOT silently edit strategy.
Drift check between recent decisions / ingestions / active hypotheses and `knowledge/strategy.md`. Read-only synthesis. Surfaces tensions for the PM to resolve; does NOT silently edit strategy.
None for a full sweep, or an optional scope:
`/strategy-check` is **read-only by default**. It does NOT edit `knowledge/strategy.md` (per CLAUDE.md "Ask the PM before changing strategy.md").
What it MAY write:
What it MUST NOT do:
The drift report, in this order:
1. **Strategy clauses under pressure** — each named clause (priority, non-goal, north-star, existing tension), with the count of decisions/hypotheses/ingestion items pressuring it, and the strongest single piece of evidence 2. **Decisions that may drift** — recent decisions whose evidence trail or scope conflicts with a named clause. One line per decision: which clause, what specifically conflicts, link to the decision file 3. **Hypotheses that may drift** — active or promoted hypotheses whose belief or test plan contradicts a named clause 4. **Ingestion signals worth watching** — recurring themes from the last ~14 days that pressure a clause but haven't yet crossed the tension threshold 5. **Proposed new tensions (drafts only)** — for any signal that DOES cross the threshold, a one-paragraph draft for `strategy.md § Tensions` with provenance, ready for PM sign-off. Default: do not apply. 6. **Closed-loop check** — any existing `strategy.md § Tensions` entry whose triggering evidence has resolved or grown stale (candidate for archival on next `/review`)
End with: "Apply any of these strategy edits? (name which / no)" — the PM's call, not yours.
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
Log a decision. Drafts a complete decision file from the existing evidence trail and surfaces it for PM sign-off.
Generate or refresh hypotheses for a feature. Works **pre-ship** (proactive, organized by the 5 risk areas) or **post-ship** (data-derived from analytics /…
Generate solution directions for a problem, grounded in what the brain already knows. Not a brainstorm. A synthesis.
Route a new artifact into the brain. Four shapes, one verb.
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…