Prompt · jalon 1
Lire les channels
Fait lire par un agent ce que personne n'a le temps de lire. Ce qui revient est une matière, pas une décision.
Fichier prompts/gate-1-channel-reading.md · texte du kit, en anglais
Have an agent read what nobody has time to read
A method by Alexis Boyer · version 4.0 · September 22, 2026
Gate 1. Ask for this by name when you want the channels or the client communications read. What comes back is input, not a decision. It ends by writing DISCOVERY.md in the project folder, which Gate 2 opens by name. It is quoted here exactly as it appears in the core guide.
What you fill in
Two brackets to replace, brackets included.
[name the channel, mailbox or thread, and the period], on the line that starts with “Read”: what the agent may read outside the project folder, and the dates, for example the support channel from March to August, or the client mailbox over the last six months. If there is nothing outside the folder, write “nothing outside the folder”: the prompt then works from the folder alone.[the product or the problem], a few lines further: what the reading is about, in a few words.
The text to copy
You are at Gate 1 of the method: gathering the discovery.
Read [name the channel, mailbox or thread, and the period]. If there is
nothing outside the folder to read, say so and work from the converted
folder alone; the rest of this prompt does not change.
Then:
- summarise what is being said about [the product or the problem];
- list what it confirms, what it contradicts, and what is new;
- name the open questions it raises for the discovery.
Then write `DISCOVERY.md` in the project folder, under these headings and no
others: the source list, the ambiguity list, the questions for stakeholders,
the hypothesis on the product boundary, the privacy and compliance risks,
and the repository, starter and template constraints. Put under them what
you read here and what the project folder already holds. Where a heading has
nothing under it, say so rather than filling it. Gate 2 opens this file by
name.
Rules:
- the project folder's own files are yours to read without asking:
`converted/` and its index, `DISCOVERY.md`, the memory and the journal;
- outside the project folder, read what I named above and nothing else: ask
me before opening any other channel, mailbox, drive or thread, every time;
- tell me exactly what you read;
- keep names, addresses and personal details out of what you write down;
- return findings, not decisions. I decide what is in scope.
`DISCOVERY.md` stays current from here on. Each time I answer one of your
questions, write what my answer settles into the file before you go on, and
say in one line what you changed there — or why there was nothing to change.
Do not hold it until the end of the conversation.
Before you finish, append an entry to the project journal — what you read
and what you wrote down — and add to the project memory only what is
genuinely settled, if anything. Then state which gate you are at, what you
have, what is missing, and what I must decide before you cross to Gate 2.
Saying what you will do next is not permission to do it: you cross when I
answer, not when you announce.