customer-learning-notes
Turn customer conversation notes, interview transcripts, call summaries, CRM snippets, or research notes into shared team learning and next questions. Use when synthesizing raw customer notes, avoiding founder interpretation bottlenecks, extracting quotes and signals, updating beliefs, or deciding what to ask next.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- customer-learning-notes
- license
- MIT
- metadata
- { "tags": "customer-discovery,research,notes,synthesis,startups", "version": "0.1.3", "category": "Marketing", "displayName": "Customer Learning Notes" }
- description
- Turn customer conversation notes, interview transcripts, call summaries, CRM snippets, or research notes into shared team learning and next questions. Use when synthesizing raw customer notes, avoiding founder interpretation bottlenecks, extracting quotes and signals, updating beliefs, or deciding what to ask next.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 2
- 参考文档agents/openai.yaml224 B
- 参考文档workflows/synthesize-conversation-notes.md1.2 KB
03 SKILL.md 正文
Customer Learning Notes
Use this skill after customer conversations to turn raw notes into team-readable evidence. Good notes make it harder to misremember, overfit, or let one founder become the sole source of customer truth.
Source Traceability
Primary source: The Mom Test by Rob Fitzpatrick, especially chapter 8 and the conclusion. Guidance is paraphrased for this MIT repo; authoring notes used converted EPUB lines 3613-4445.
Signal Taxonomy
Use these labels when synthesizing notes:
| Label | Meaning |
|---|---|
| Pain | Problem, obstacle, annoyance, risk, or cost |
| Goal | Desired outcome, job to be done, or priority |
| Workaround | Current manual process, tool stack, hack, or substitute |
| Money | Budget, cost, value, purchase process, or decision owner |
| Person | Specific stakeholder, competitor, team, buyer, or intro lead |
| Feature | Request, buying criterion, integration need, or implementation clue |
| Emotion | Strong excitement, anger, embarrassment, fear, or skepticism |
| Follow-up | Promise, task, intro, research item, or next step |
Synthesis Workflow
- Preserve concrete facts separately from interpretation.
- Pull out short, useful quotes only when they are needed for traceability, positioning, or internal alignment.
- Tag signals using the taxonomy above.
- Group evidence by segment, problem, workaround, budget, and commitment.
- Identify contradictions and mixed-segment noise.
- Update beliefs, risks, and the next three questions.
- Recommend whether to continue, narrow the segment, ask for commitments, or move to building/testing.
Confidence Levels
| Level | Use When |
|---|---|
| High | Repeated behavior from a focused segment, with concrete cost or commitment. |
| Medium | Specific evidence from a few good-fit conversations. |
| Low | One-off quotes, mixed segments, opinions, or weakly anchored claims. |
Output Format
# Customer Learning Synthesis
## Source Notes
- Conversations:
- Segment:
- Date range:
## Evidence
| Signal | Evidence | Segment | Confidence | Implication |
|--------|----------|---------|------------|-------------|
## Belief Updates
- Stronger / weaker / new / rejected:
## Decisions
- Product, segment, positioning, sales or access:
## Next 3 Questions
1. [Question]
2. [Question]
3. [Question]
Workflow
Use workflows/synthesize-conversation-notes.md when the user provides raw
notes, transcripts, call summaries, or interview excerpts.
Quality Bar
- Do not summarize notes into vibes.
- Do not let one loud quote outweigh repeated behavior from a focused segment.
- Do not mix segments without labeling them.
- Do not treat notes as useful until they have been reviewed and turned into updated beliefs or decisions.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.