Discovery notes
Turns raw notes from customer conversations into a structured discovery document. Use when the user pastes meeting notes, a call transcript or interview notes and wants them organised.
Skill · works with Claude Code, or any agent that loads SKILL.md files
Install it for your user (or swap ~/.claude for .claude to add it to one project):
mkdir -p ~/.claude/skills/discovery-notes && curl -fsSL https://imsus.dev/skills/discovery-notes/SKILL.md -o ~/.claude/skills/discovery-notes/SKILL.mdShow SKILL.md
---
name: discovery-notes
description: "Turns raw notes from customer conversations into a structured discovery document. Use when the user pastes meeting notes, a call transcript or interview notes and wants them organised."
---
# Discovery notes
Turn raw customer conversation notes into a discovery document the team can act on.
## Steps
1. Read every note before writing. List the people mentioned and their roles.
2. Separate what the customer said from what the note-taker concluded. Quote the customer where the notes allow.
3. Write the document with these sections, in order:
- **Goal**: what the customer is trying to achieve, in one paragraph.
- **Today**: how the work is done now, step by step, including manual steps and workarounds.
- **Pain**: problems in their words, each with any number or example given.
- **Constraints**: security, compliance, data access, deadlines, budget.
- **People**: who decides, who uses, who blocks.
- **Open questions**: what must be asked next, most important first.
4. End with the single next step you would take, and why.
## Rules
- Never invent numbers, names or quotes. Write "not mentioned" instead.
- Keep the customer's terms for things; add the team's term in brackets if it differs.
- If notes from several calls disagree, list both versions and the date of each.Also at /skills/discovery-notes/SKILL.md.