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.

Informações da origem

Repositório
protosphinx/sphinxstack
Última atividade na origem
29 de julho de 2026 às 13:55
Idioma detectado do SKILL.md
inglês
Estrelas
3
Forks
0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
2 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
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
Ver no GitHub