Wonbeen Lee wbeen / AI Product Ops notebook
Operating index

Knowledge Map

A public connection layer for the notebook.

The Knowledge Map is a static index of public assets and the relationships between them. It is intentionally quiet: useful for humans scanning the archive and for agents deciding what to read next.

Start exploring

Choose a path into the map. Each shortcut opens a focused view below.

Visual network preview

Interactive connection map.

topic article prompt other content

Map by content type

Typed public assets.

Each card keeps the same stable fields exposed in /content-graph.json: id, type, URL, summary, topics, and tags.

article

articles/a-prompt-library-is-not-enough A Prompt Library Is Not Enough Claims that prompt dumps decay; durable value comes from workflows with typed inputs/outputs, use cases, and safety notes. articles/ai-product-planning-hub-pipeline-governance My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance Introduces a three-layer operating model for AI-assisted product planning — Hub for multi-tool reality, Pipeline for standardized deliverables, Governance for repeatable team gains. articles/ai-product-planning-pm-role My journey of bringing AI into Product Planning (Part 5) — What this changed about the PM role Closes the series by arguing that AI relocates product judgment rather than removing it, shifting the PM role toward context design, workflow design, and lightweight governance. articles/ai-product-planning-process-redesign My journey of bringing AI into Product Planning (Part 1) — Why AI adoption forced a process redesign Argues that AI makes drafting cheap and misalignment expensive, and that adopting AI in product planning requires redesigning the process (deliverables + quality gates), not just picking a tool. articles/ai-product-planning-repeatable-use-cases My journey of bringing AI into Product Planning (Part 3) — Repeatable use cases inside the workflow Describes four AI use cases in product planning (documentation, research support, prototyping, review) that mattered because they connected to the surrounding workflow rather than existing as one-off outputs. articles/ai-product-planning-team-capability My journey of bringing AI into Product Planning (Part 4) — From personal prompts to team capability Argues that scaling AI in product planning requires moving from individual prompt skill to reusable team capability, built on clear inputs, stable outputs, shared standards, and interconnected workflow components. articles/ai-rollout-after-setup The rollout starts after setup Published LinkedIn post on Claude adoption in product planning, emphasizing that AI systems need source hygiene, skill improvement, output review, team sharing, and lightweight governance after setup. articles/evidence-first-ai-workflow Before Asking AI to Change Anything: An Evidence-first Inspect, Verify, and Audit Workflow Guide to an evidence-first AI work sequence: inspect the current state, turn requirements into observable checks, make the smallest justified change, verify with tool evidence, and stop or escalate when evidence is unavailable. Links to Prompt Hotbar prompts and the coding-agent workflow. articles/fable-5-audit-the-checklist Fable 5: Audit the Checklist That Approved the Work Published LinkedIn post on using Fable 5 to audit completed work, distinguish recorded and reflected evidence from execution verification, and challenge the checklist itself. articles/prompt-hotbar-local-mcp-pilot From Prompt Clipboard to Local MCP: Testing Prompt Hotbar Inside Claude Code Proof-of-work note on a private Prompt Hotbar MCP pilot in Claude Code. A local stdio server exposed five read-only tools for prompt search, prompt retrieval, recommendation, workflow search, and workflow retrieval. The pilot returned reviewed public-safe catalog data only: 23 prompts and 3 workflows. npm publication remained intentionally withheld. articles/why-im-building-a-personal-ai-operating-site Why I'm Building a Personal AI Operating Site Argues that personal sites should evolve from portfolios into typed, AI-readable knowledge products with explicit public/private boundaries. articles/why-youtube-opened-pip-kept-background-play Why YouTube Opened PiP but Kept Background Play Premium Analyzes YouTube's decision to free Picture-in-Picture while keeping background play Premium, arguing the split reflects a monetization boundary between a visual attention surface and an audio-first paid habit.

lab

note

project

prompt

reference

skill

template

workflow

Topic clusters

Where ideas collect.

topic

agentic-workflow

topic

agentic-workflows

topic

ai-coding

topic

AI Product Ops

topic

ai-product-planning

topic

ai-readable

topic

ai-workflow

topic

alignment

topic

b2b-saas

topic

boundary

topic

context

topic

context-handoff

topic

developer-tools

topic

extraction

topic

governance

topic

handoff

topic

knowledge-capture

topic

knowledge-ops

topic

knowledge-product

topic

local-first

topic

mcp

topic

metadata

topic

monetization

topic

personal-kb

topic

planning-workflow

topic

product-ops

topic

product-strategy

topic

productivity

topic

prompt-reuse

topic

prompts

topic

prototype

topic

publishing

topic

publishing-pipeline

topic

reuse

topic

site-structure

topic

standards

topic

user-behavior

topic

verification

topic

workflow-design

topic

workflows

Connected assets

Manual and derived relationships.

A Prompt Library Is Not Enough documents lab Chat Conversation Mining for Public Knowledge

A Prompt Library Is Not Enough has template AI-Readable Site IA Planner

My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance part of series My journey of bringing AI into Product Planning (Part 5) — What this changed about the PM role

My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance part of series My journey of bringing AI into Product Planning (Part 1) — Why AI adoption forced a process redesign

My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance related to My journey of bringing AI into Product Planning (Part 1) — Why AI adoption forced a process redesign

My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance part of series My journey of bringing AI into Product Planning (Part 3) — Repeatable use cases inside the workflow

My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance related to My journey of bringing AI into Product Planning (Part 3) — Repeatable use cases inside the workflow

My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance part of series My journey of bringing AI into Product Planning (Part 4) — From personal prompts to team capability

My journey of bringing AI into Product Planning (Part 5) — What this changed about the PM role part of series My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance

My journey of bringing AI into Product Planning (Part 5) — What this changed about the PM role part of series My journey of bringing AI into Product Planning (Part 1) — Why AI adoption forced a process redesign

My journey of bringing AI into Product Planning (Part 5) — What this changed about the PM role part of series My journey of bringing AI into Product Planning (Part 3) — Repeatable use cases inside the workflow

My journey of bringing AI into Product Planning (Part 5) — What this changed about the PM role part of series My journey of bringing AI into Product Planning (Part 4) — From personal prompts to team capability

My journey of bringing AI into Product Planning (Part 5) — What this changed about the PM role related to My journey of bringing AI into Product Planning (Part 4) — From personal prompts to team capability

My journey of bringing AI into Product Planning (Part 1) — Why AI adoption forced a process redesign part of series My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance

My journey of bringing AI into Product Planning (Part 1) — Why AI adoption forced a process redesign related to My journey of bringing AI into Product Planning (Part 2) — Hub, pipeline, and governance

My journey of bringing AI into Product Planning (Part 1) — Why AI adoption forced a process redesign part of series My journey of bringing AI into Product Planning (Part 5) — What this changed about the PM role

My journey of bringing AI into Product Planning (Part 1) — Why AI adoption forced a process redesign part of series My journey of bringing AI into Product Planning (Part 3) — Repeatable use cases inside the workflow

My journey of bringing AI into Product Planning (Part 1) — Why AI adoption forced a process redesign part of series My journey of bringing AI into Product Planning (Part 4) — From personal prompts to team capability