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-06-26
- Stars
- ★ 0
- Forks
- 0
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
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.