Templates
Seven Markdown templates, ready to use. Each one carries the criteria that came out of the evidence on this site. At the end of each, the “Why this is here” section names the criterion and its source.
How to use them
Section titled “How to use them”- Open a template and copy the block with the button in its corner.
- Paste it into your repository or your documents tool.
- Fill in the fields in brackets. Instructions sit inside
<!-- -->. Delete them when you finish.
The same files live in the templates/ folder of the repository, in Spanish and English.
The seven
Section titled “The seven”| Template | What it is for | When |
|---|---|---|
| ADR: agent, fixed workflow or person? | Decide whether the task needs an agent and record the reason. An ADR is a record of an architecture decision. | Before building. |
| Design review | Review the design in order, from the task to operations. | Before writing code. |
| Threat map | Find where untrusted content, sensitive data and external actions meet. | Before granting access to real tools. |
| Evaluation plan | Measure with real tasks and pass^k (all attempts go right), and set when it ships and when it rolls back. | Before users see it. |
| Action policy | Put each action in automatic, confirm or forbidden. | Before connecting tools that write. |
| Incident runbook | Stop the damage, diagnose from the log and communicate. A runbook is a guide with steps for an incident. | Before going to production. |
| Cost sheet | Compute cost per successful task, with retries and human review. | When deciding, and whenever prices change. |
In what order
Section titled “In what order”Start with the ADR, because it can end in “we do not need an agent”. The design review requires the other six. Write the runbook before you go to production: during the first incident, you will not have time.