Leandro Arroyo

1. 01

   The idea gets argued before it gets written

   Before any line of code the idea is argued and defended: what it solves, for whom, under what constraints, with what architecture and at what cost. That argument produces a written concept, not a hunch.

2. 02

   Rounds of questions

   The first version of the idea is never treated as final. The existing code gets explored and the questions come back in rounds: gaps, contradictions, edge cases, pending calls. Only once those are settled does anything get written.

3. 03

   One task document

   Those answers produce a single document: objective, scope, acceptance criteria and a list of verifiable tasks. Not bureaucracy: it is being able to say at any moment what is done and what is left, and to pick the thread back up if the work gets interrupted.

4. 04

   Task by task, commit by commit

   Each task takes the smallest path that does the job, tests first, and closes with its own commit. Small work stays small: not everything needs a document. Agents run inside those limits, and they are not the ones who set them.

5. 05

   Judges and tests

   Nothing is accepted because it looks right: every task has to meet its criteria, pass its tests and survive a review. If it does not pass, it does not matter who wrote it.

The tool executes. The decisions are not delegated.