Skip to main content

conduct-a-case-study-interview

Gather attributable customer evidence through a prepared and consent-based interview. Use when a case study needs verified context, process, contribution, results, limitations, and approval rather than a promotional testimonial.

Quellinformationen

Repository
protosphinx/sphinxstack
Letzte Quellaktivität
29. Juli 2026 um 13:55
Erkannte Sprache von SKILL.md
Englisch
Sterne
3
Forks
0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
2 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
conduct-a-case-study-interview
category
write
description
Gather attributable customer evidence through a prepared and consent-based interview. Use when a case study needs verified context, process, contribution, results, limitations, and approval rather than a promotional testimonial.
# conduct-a-case-study-interview Collect the customer's account without forcing it into a predetermined success story. ## Procedure 1. Confirm interview purpose, participant authority, incentives, recording, attribution, review, use, and withdrawal terms. 2. Research the organization, situation, implementation, available metrics, known problems, and sensitive boundaries. 3. Write open questions covering before state, decision, alternatives, implementation, effort, contribution, result, limitation, and next step. 4. Share scope and consent terms in advance without scripting answers. 5. At the start, reconfirm recording and attribution and explain how quotes and facts will be reviewed. 6. Ask for specific examples, time periods, definitions, sources, and counterexamples. 7. Distinguish participant observation, organizational records, inference, and opinion in the notes. 8. Probe negative outcomes, workarounds, dependencies, and what the product did not cause. 9. Summarize key claims back to the participant and list evidence or approvals still required. 10. Preserve the recording securely, prepare a source log, and route quotes and claims through agreed review. ## Guardrails - Never invent, polish beyond meaning, or pressure a participant to endorse a claim. - Protect customers, employees, end users, and confidential business information. - A gift or incentive must not be conditioned on positive statements. - Do not publish a metric without its definition, source, period, and approval. ## Done - Interview notes or recording preserve consent, context, attribution, and exact claims - A source log separates verified facts, participant statements, and open evidence - The participant receives the agreed factual and quotation review - Sensitive material and use limits are recorded
Auf GitHub ansehen