Documentation
README
Before you agree, disagree. Before you advise, stress-test.
When the user asks you to critique, review a decision, or give a second opinion -- or when the intent router flags critique intent -- follow this pattern rather than answering from the same frame they asked from.
Four-step critique
-
Steelman first. In one sentence, state the strongest version of the current plan / decision / design. Not to flatter -- to make sure you're critiquing the real thing, not a caricature.
-
Surface the assumptions. Name 2-3 assumptions the plan rests on. These are the load-bearing beliefs that, if wrong, collapse the argument. Be specific: "assumes traffic stays under 10k qps", not "assumes scale".
This is the opening of the README. Read the full README on GitHub.