customer-call-to-prd
Skill0 starsChanged 5 months agoMITView on GitHub
Use when converting customer call notes, interview transcripts, sales discovery notes, or PM research fragments into a concise PRD with user problems, requirements, non-goals, and risks.
In this repository19 other files it gives its agents.
- agent-handoff-briefSkill
- api-doc-to-tool-specSkill
- architecture-rfc-reviewSkill
- bug-report-to-reproSkill
- changelog-to-upgrade-planSkill
- competitive-research-briefSkill
- database-migration-risk-reviewSkill
- dependency-upgrade-risk-reviewSkill
- incident-log-to-postmortemSkill
- messy-notes-to-decision-logSkill
- privacy-data-flow-mapSkill
- prompt-to-eval-rubricSkill
- repo-launch-readiness-reviewSkill
- roadmap-to-release-planSkill
- security-review-checklistSkill
- support-ticket-to-evalSkill
- telemetry-to-product-insightsSkill
- tool-permission-auditSkill
- workflow-automation-scoutSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use when customer research needs to become requirements without losing the original evidence.
- Distinctive: line 15
Do not use when the user already has a finalized PRD and only needs copyediting.
- Distinctive: line 19
Call notes, transcript snippets, interview notes, or sales discovery notes.
- Distinctive: line 29
Add risks, dependencies, and open questions for PM follow-up.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Customer Call To PRD
Purpose
Transform customer conversation material into a product requirement draft that preserves evidence and uncertainty.
Fit
- Use when customer research needs to become requirements without losing the original evidence.
- Do not use when the user already has a finalized PRD and only needs copyediting.
Inputs
- Call notes, transcript snippets, interview notes, or sales discovery notes.
- Customer segment, product area, and known business goal if available.
- Existing constraints, deadlines, or roadmap context.
Workflow
- Extract user problems before proposing features.
- Separate direct customer evidence from internal interpretation.
- Group repeated needs into requirements.
- Define non-goals to prevent scope creep.
- Add risks, dependencies, and open questions for PM follow-up.
Output
Produce Markdown with:
- Customer Context
- Problem Statements
- Requirements
- Non-Goals
- Evidence
- Risks And Dependencies
- Open Questions
Validation
- Requirements trace back to call evidence.
- Internal guesses are labeled as interpretation.
- Non-goals are explicit.
- The PRD does not promise delivery dates unless provided.
- Open questions are specific enough for a follow-up call.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

