Find ADR candidates

An ADR records a lasting architectural choice and its reason. Do not create one for every code change. Ask the agent to use the repository record as evidence before it writes an ADR.

Give the agent this order

1. Run criv init from the repository root.
2. Read the existing documentation and ADRs.
3. If they are available, read past project conversations for decisions and their reasons.
4. Compare that evidence with the current code.
5. Write ADRs for lasting decisions that the evidence supports.
6. Run criv watch --once and criv check.

Useful questions

• Which choice changes the structure, boundary, data model, or delivery path?
• What alternatives were considered, and why was this one selected?
• Which source paths does the decision govern?
• Does an existing ADR already record the decision?

If evidence is missing, the agent should leave the decision open or ask for it. It should not invent history.

Return to setup or read the repository documentation.