- Home
- Skills
- Business & Operations
- PM Second Brain
More screenshots
Works with the AI Agents you already use
PM Second Brain
A product manager's working memory in plain files: calls in, decisions, promises and feedback out, and every answer checked against what is on record.
$9
PM Second Brain
Example session with this skill installed
Brief me before my call with Fennimore Dental
The project already has a memory/ folder from earlier runs: three call notes, one email, two decision records and a promise list. Rotawise is a fictional shift-scheduling app for clinics.
- Read your context and instructions
- Compiled the pm second brain
- Generated the document
Summary: a one-page brief built only from memory: two decisions that disagree, a promise 18 days overdue, three mentions of one theme from one customer, and four questions to ask.
Mode: prep. One page, built only from memory/. Window for counts: 2026-08-19 to 2026-11-17 (90 days).
Brief: Fennimore Dental · 2026-11-17
Recent calls
- 2026-10-29: Tomas spoke with Fennimore's ops lead and the FD Clinic night-team lead. Both want a sign-off on night swaps; day swaps stay instant. call note
- 2026-09-15: the clinic manager approves every swap by hand and wants that gone; Tomas promised the export spec. call note
Decisions involving them
No decision record names Fennimore. These two are on the theme they raised three times, shift-swap approvals, newest first:
- 2026-10-08,
evidence, pending confirmation: "From now on night-shift swaps need a manager's approval." (Mara) record
- 2026-08-20,
instruction, review by 2027-02-20: "Shift swaps never need manager approval." (Mara) record
These two disagree. The newer one supersedes the older, but the older is confirmed and stays in force until Mara confirms the newer one. The choice is hers.
Open promises
- To them,
overdue by 18 days: P-001, Tomas, send the export spec, due 2026-10-30. "I'll send you the export spec by 30 October." (2026-09-15) On 2026-10-29 Tomas said the spec was still being written. promises
- From them: nothing in memory.
Their feedback by theme
Shift-swap approvals: 3 mentions, 1 distinct customer, 2026-08-19 to 2026-11-17. Fennimore Dental, Fennimore and FD Clinic are one customer in customers.
- 2026-10-29: "Keep day swaps instant. Only the night ones need a sign-off." (FD Clinic night-team lead) item
- 2026-10-29: "Night swaps are where we get burned, so for nights a manager should sign off." (Fennimore ops lead) item
- 2026-09-15: "We need swaps to go through without waiting on me. At the moment I approve every one by hand." (clinic manager) item
Other themes from Fennimore: nothing in memory.
Open questions from earlier calls
- Holiday calendar sync: the clinic manager asked about it and Tomas said "We'll look into the holiday calendar sync." That is a vague intention, not a promise, so no owner or date exists. call note
Questions to ask
- The export spec is 18 days overdue. When can they expect it, and does payroll still need it monthly? (from the overdue promise)
- In September they wanted no approval on swaps; in October they asked for sign-off on nights. Is the night-only rule what they want? (from their feedback)
- Does a manager sign-off on night swaps mean a named person per clinic? Nothing in memory says who approves. (from the unconfirmed decision)
- Is holiday calendar sync still wanted, and by when? (from the open question)
Next steps
memory/dashboard.htmlopened on the prep tab. The decisions tab shows the two disagreeing records side by side; the promises tab marks P-001 overdue.- After the call, say "process this call" with the transcript. New decisions, feedback and promises land in
memory/as evidence, and the brief for the next call starts from them. - Say "confirm the night-shift swap record, confirmed by Mara" once Mara agrees. The skill asks for a review date, then the older rule is superseded and leaves the index.
dashboard.html
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
A product manager's week is calls, threads and documents, and most of what was said is gone by Friday. PM Second Brain files each conversation as small markdown notes inside your project, then answers from them: what was decided, what was promised, what customers keep asking for.
The working loop has nine modes:
- Call: turns a transcript, notes or an email into decision records, feedback items and promise rows, each with its own word-for-word quote. Ideas and vague intentions are listed as "not captured", with a reason.
- Prep: a one-page brief before a customer call. Recent calls, decisions, open promises with the overdue ones first, feedback counted by theme, open questions, and questions to ask.
- Spec: a draft that starts with what memory already holds. Every requirement links a record; anything without a source becomes an open question.
- Check: reads a document before it goes out and reports what is missing, what is wrong and what was verified. It catches a year-to-date figure set against a full-year target.
- Feedback, weekly, ask, confirm: counts by theme with distinct customers, a weekly page, recall of any decision with its quotes, and the step where you confirm.
The memory stays checked. Anything the skill writes is evidence. Only you turn it into an instruction, by saying yes. A later decision that contradicts a confirmed one is shown beside it as pending confirmation, and nothing is overwritten. Each confirmed decision carries a review date, and an audit mode lists records whose date has passed, promises past due, broken sources and links.
Some modes also leave a local dashboard page you can open in any browser, with no network.
It reads records written by PM Brain Core as they are, and PM Brain Core is not needed: PM Second Brain works installed alone.
It works on plain files with no accounts or services, writes only inside your project and never posts or sends anything.
Requires local file system access. Only tracks data manually provided in the project folder. Does not sync with external tools like Jira or Slack.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed today