Analyser et écrire le PRD

Analyse the discovery and write the PRD

A method by Alexis Boyer · version 4.0 · September 22, 2026

Gate 2. The second prompt of the setup. It reads what Gate 0 and Gate 1 left in the folder and writes the PRD into the template. It is quoted here exactly as it appears in the core guide.

The text to copy

You are at Gate 2 of the method: writing the PRD.

Read, and open nothing else without asking me first:
- the converted folder `converted/` and its index `converted/INDEX.md`;
- `DISCOVERY.md` in the project folder: the source list, the ambiguity list
  and the stakeholder questions written at Gate 1, including what an agent
  read on my behalf;
- the project memory and the project journal;
- the PRD template `../templates/prd.md`, for the shape of each section.

Anything that is not in the project folder — a channel, a mailbox, client
communications — is named here by me, or it is not read.

First, state three things, separately:
1. what is established, and which source establishes it;
2. what contradicts what, source against source, without resolving it
   yourself;
3. what is absent — the questions this material does not answer.

Then ask me the alignment questions. Where two sources point different ways,
do not choose silently. For each one, give me: what source A says, what
source B says, the product risk of choosing the wrong interpretation, the
direction you would default to, and the confirmation you need from me.

Then produce one document: the PRD, with these fourteen sections, in this
order, and no others:
1. strategic framing — what the product is going to be, what is wanted and
   what is not, the boundary it holds, the business loop it serves;
2. product boundary;
3. roles and permissions;
4. core workflows;
5. product states and data visibility;
6. privacy and ethics rules;
7. which source wins when sources disagree;
8. design baseline and acceptable drift;
9. functional depth;
10. backlog taxonomy;
11. backend and API assumptions;
12. acceptance criteria;
13. the QA contract;
14. open decisions.

Rules:
- one document, not two: the strategic framing is the PRD's first section,
  and the sections after it detail what it states;
- mark every assumption as an assumption, with the source it rests on or,
  when the material does not settle it, what is missing and who has to
  decide it;
- invent no decision, no approval, no API and no standard; if it is not in
  the material, it is absent, and absent is an answer;
- do not send anything anywhere — no service, no channel, no address.

Before you finish, state which gate you are at, what you have, what is
missing, and what I must decide before you cross to Gate 3.