/ideate
Generate solution directions for a problem, grounded in what the brain already knows. Not a brainstorm. A synthesis.
$ 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
/ideate
Context preview
What this command does when you run it.
Generate solution directions for a problem, grounded in what the brain already knows. Not a brainstorm. A synthesis.
Command definition
ideate.md/ideate
Generate solution directions for a problem, grounded in what the brain already knows. Not a brainstorm. A synthesis.
Input
A problem statement, an opportunity, or a `knowledge/users/insights.md § <theme>` reference. Example: `/ideate onboarding drop-off in mid-market`.
Loads
- `knowledge/strategy.md` (priorities, non-goals, north-star)
- `knowledge/users/insights.md` and any matching `personas.md` / `segments.md`
- Active `hypotheses/` files in the same area
- Recent `decisions/` that constrain or invalidate options
- `knowledge/market/competitors/` and `trends.md` for adjacent moves
- `rules/discovery.md` and `rules/prioritization.md` if present
Updates
Drafts only. Nothing committed at call time.
- A draft `ingestion/adhoc/<date>-ideate-<slug>.md` capturing the session
- Hypothesis candidates queued under `hypotheses/<slug>.md § Candidates` (PM confirms before promotion)
Surfaces
- 3-7 solution directions, each tagged with the evidence supporting it (insight, hypothesis, decision, or market signal)
- For each direction: which strategy priority it serves, which non-goal it might violate, which active hypothesis it would test or contradict
- 1-2 directions explicitly marked as **off-strategy** if surfaced, so the operator can decide whether to pivot strategy or reject the direction
- The thinnest viable next step for the top 2 (a discovery question, an experiment, a competitor study)
Anti-pattern: do not generate directions that ignore the strategy doc or the non-goals. If the evidence forces an off-strategy direction, surface the tension instead of swallowing it.
Read more
/ideate
Generate solution directions for a problem, grounded in what the brain already knows. Not a brainstorm. A synthesis.
Input
A problem statement, an opportunity, or a `knowledge/users/insights.md § <theme>` reference. Example: `/ideate onboarding drop-off in mid-market`.
Loads
- `knowledge/strategy.md` (priorities, non-goals, north-star)
- `knowledge/users/insights.md` and any matching `personas.md` / `segments.md`
- Active `hypotheses/` files in the same area
- Recent `decisions/` that constrain or invalidate options
- `knowledge/market/competitors/` and `trends.md` for adjacent moves
- `rules/discovery.md` and `rules/prioritization.md` if present
Updates
Drafts only. Nothing committed at call time.
- A draft `ingestion/adhoc/<date>-ideate-<slug>.md` capturing the session
- Hypothesis candidates queued under `hypotheses/<slug>.md § Candidates` (PM confirms before promotion)
Surfaces
- 3-7 solution directions, each tagged with the evidence supporting it (insight, hypothesis, decision, or market signal)
- For each direction: which strategy priority it serves, which non-goal it might violate, which active hypothesis it would test or contradict
- 1-2 directions explicitly marked as **off-strategy** if surfaced, so the operator can decide whether to pivot strategy or reject the direction
- The thinnest viable next step for the top 2 (a discovery question, an experiment, a competitor study)
Anti-pattern: do not generate directions that ignore the strategy doc or the non-goals. If the evidence forces an off-strategy direction, surface the tension instead of swallowing it.
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 - /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 - /prep
Surface what to ask, raise, or watch for in an upcoming conversation.
Open command - /review
The weekly maintenance sweep. Six checks. Produces a dated report and edits files directly where confidence is high.
Open command