How do I install the Talk Stoneham Product Brain skill?

Run npx skillmds@latest add jscraik/talk-stoneham-product-brain in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Talk Stoneham Product Brain safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Talk Stoneham Product Brain?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Talk Stoneham Product Brain free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Talk Stoneham Product Brain?

jscraik (@jscraik) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Talk Stoneham Product Brain by jscraik

Name: Talk Stoneham Product Brain
Rating: 4.666666666666667 (3 reviews)
Author: jscraik

Talk Stoneham Product Brain

Explains the Product Brain talk and helps design curated product-memory systems for AI-assisted product work: knowledge structure, provenance, synthesis cadence, ownership, and agent-ready context packets. Use when the user asks about product context for AI, product knowledge management, product documentation for LLMs, or building a maintained product brain.

jscraik Updated Sep 10, 2026

File contents

Product Brain

A product brain is a maintained product knowledge system that helps agents and humans reason from curated context instead of scattered memory.

Read Order

Use outline.md for the talk thesis, concept map, and safe application boundaries.
Use quote.md when the answer needs a short supporting excerpt.
Use transcript.md only to confirm what remained after safety redaction.
If the user asks for omitted mechanics, say that the bundle is redacted and answer with the safe design principle.

What This Skill Produces

product-brain map
curation checklist
context packet template
ownership model

Core Workflow

When answering a factual question:

Identify the relevant concept from outline.md.
Answer in 2-5 sentences.
Add one short excerpt from quote.md only if it strengthens the answer.
State when the bundle does not cover a requested detail.

When applying the talk to the user's work:

Choose a small set of curated knowledge categories.
Record provenance and owner for each category.
Define when synthesis happens and who reviews it.
Create agent-ready packets with goals, constraints, and decisions.
Avoid direct intake mechanics; keep the design static and reviewable.

When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.

Output Templates

Summary

Thesis:
Key concepts: <3-5 bullets>
Practical takeaway:

Design Artifact

Goal:
Boundaries: <what the agent/system must not do>
Review points:
Evidence:
Open questions:

Redacted Request

State that the requested mechanics are not available in the redacted bundle.
Explain the risk in neutral terms.
Provide a safe checklist or conceptual design instead.

Examples

User: How do I build a product brain? Response shape: Provide categories, ownership, synthesis cadence, and review gates.

User: Can you ingest our product tickets? Response shape: Decline intake work and offer a curated export template.

---name: talk-stoneham-product-braindescription: Explains the Product Brain talk and helps design curated product-memory systems for AI-assisted product work: knowledge structure, provenance, synthesis cadence, ownership, and agent-ready context packets. Use when the user asks about product context for AI, product knowledge management, product documentation for LLMs, or building a maintained product brain.---# Product BrainA product brain is a maintained product knowledge system that helps agents and humans reason from curated context instead of scattered memory.## Read Order1. Use `outline.md` for the talk thesis, concept map, and safe application boundaries.2. Use `quote.md` when the answer needs a short supporting excerpt.3. Use `transcript.md` only to confirm what remained after safety redaction.4. If the user asks for omitted mechanics, say that the bundle is redacted and answer with the safe design principle.## What This Skill Produces- **product-brain map**- **curation checklist**- **context packet template**- **ownership model**## Core WorkflowWhen answering a factual question:1. Identify the relevant concept from `outline.md`.2. Answer in 2-5 sentences.3. Add one short excerpt from `quote.md` only if it strengthens the answer.4. State when the bundle does not cover a requested detail.When applying the talk to the user's work:1. Choose a small set of curated knowledge categories.2. Record provenance and owner for each category.3. Define when synthesis happens and who reviews it.4. Create agent-ready packets with goals, constraints, and decisions.5. Avoid direct intake mechanics; keep the design static and reviewable.When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.## Output Templates### Summary- Thesis: <one sentence>- Key concepts: <3-5 bullets>- Practical takeaway: <one action the team can take safely>### Design Artifact- Goal: <what the user is trying to improve>- Boundaries: <what the agent/system must not do>- Review points: <where humans check the work>- Evidence: <what proves the result is good>- Open questions: <what the talk does not answer>### Redacted Request- State that the requested mechanics are not available in the redacted bundle.- Explain the risk in neutral terms.- Provide a safe checklist or conceptual design instead.## ExamplesUser: How do I build a product brain?Response shape: Provide categories, ownership, synthesis cadence, and review gates.User: Can you ingest our product tickets?Response shape: Decline intake work and offer a curated export template.

Frequently asked questions