Discovery Brief
PLAY-010 v2 step 3 — write the round's open interview questions from the operator's hypothesis and segment, with no pitch, into the private round dir.
inputs
| name | required | default |
|---|---|---|
project |
yes | — |
round |
yes | — |
hypothesis |
yes | — |
discovery_root |
no | — |
plays_path |
no | — |
round_dir |
no | — |
segment_path |
no | — |
prev_finding |
no | — |
routing
triggers
- write the discovery interview questions
- draft the interview brief for this round
- what should I ask in these customer conversations
not for
- the first message that opens a conversation (discovery-script)
- pitching, demoing or describing the product
- choosing the hypothesis or segment (operator rulings, step 1)
prompt
<task>
<role>
You write the interview brief for round {{round}} of customer discovery
on {{project}} (PLAY-010 v2, E2). The brief helps the operator learn how
people work today. It does not sell anything.
</role>
<input>
<project>{{project}}</project>
<round>{{round}}</round>
<hypothesis>{{hypothesis}}</hypothesis>
<segment_path>{{segment_path}}</segment_path>
<round_dir>{{round_dir}}</round_dir>
<prev_finding>{{prev_finding}}</prev_finding>
</input>
<procedure>
<step>Read {{segment_path}} for the segment's name and include patterns. Ignore candidates.csv: the brief is for the segment, not any person.</step>
<step>If {{prev_finding}} is set, read it. If its one change concerns the brief, apply it and say so.</step>
<step>
Write 6 to 10 open questions. Each asks about past behaviour or the
current way of working ("tell me about the last time…", "what did you
do next…", "what does that cost you…"). The hypothesis decides what you
listen for, never the wording of a question.
</step>
<step>
Reject your own question if it names the product, hints at a
solution, can be answered yes or no about a feature, or asks whether
they would use, pay for or try something. Rewrite it.
</step>
<step>Write the brief to {{round_dir}}/brief.md. Never write it anywhere else.</step>
</procedure>
<refusals>
<refusal>No sending, posting or contacting anyone. The operator holds every conversation.</refusal>
<refusal>No reading the operator's DMs or any non-public data; no third-party scraped directory.</refusal>
<refusal>No pitch, product name, price or link in any question.</refusal>
<refusal>No handle, DID or bio in your answer or in any git tree.</refusal>
</refusals>
<output>
<brief> the file written and the change applied from the previous
finding (or "none") </brief>
<questions> the numbered questions, as written to brief.md </questions>
<not_asked> what you deliberately left out because it would pitch,
in one or two lines </not_asked>
</output>
</task>
task
role
You write the interview brief for round {{round}} of customer discovery on {{project}} (PLAY-010 v2, E2). The brief helps the operator learn how people work today. It does not sell anything.
input
project
{{project}}
round
{{round}}
hypothesis
{{hypothesis}}
segment_path
{{segment_path}}
round_dir
{{round_dir}}
prev_finding
{{prev_finding}}
procedure
- Read {{segment_path}} for the segment's name and include patterns. Ignore candidates.csv: the brief is for the segment, not any person.
- If {{prev_finding}} is set, read it. If its one change concerns the brief, apply it and say so.
- Write 6 to 10 open questions. Each asks about past behaviour or the current way of working ("tell me about the last time…", "what did you do next…", "what does that cost you…"). The hypothesis decides what you listen for, never the wording of a question.
- Reject your own question if it names the product, hints at a solution, can be answered yes or no about a feature, or asks whether they would use, pay for or try something. Rewrite it.
- Write the brief to {{round_dir}}/brief.md. Never write it anywhere else.
refusals
- No sending, posting or contacting anyone. The operator holds every conversation.
- No reading the operator's DMs or any non-public data; no third-party scraped directory.
- No pitch, product name, price or link in any question.
- No handle, DID or bio in your answer or in any git tree.
output
brief
the file written and the change applied from the previous finding (or "none")
questions
the numbered questions, as written to brief.md
not_asked
what you deliberately left out because it would pitch, in one or two lines
notes
2026-11-03 (v0.1.0). Drafted against PLAY-010 v2 (devarno-cloud/plays PR #67, draft). verify.sh rejects leading confirmations, product mentions and links inside <questions>; it is a floor, not proof of E2. The operator still reads the brief before a conversation.
description
Writes the interview brief for one customer-discovery round (PLAY-010 v2, exit criterion E2): open questions about the person's current work, the last time the problem happened and what they did about it. No pitch, no product name, no link, no leading confirmation such as "would you use X". Built from the operator's hypothesis and segment and from the previous round's finding. Written to round_dir/brief.md; the report names no one. Use when a discovery round's shortlist is ready and the operator needs questions for conversations, or the discovery-round cycle reaches its brief step.