Karpathy Execution Gate

Role

Run a short discipline gate right before implementation to reduce over-engineering and scope drift.

When to use

• Immediately before the first implementation-runner call for medium/complex tasks
• Re-run when plan assumptions or scope boundaries change

Inputs

• analysisContext.request, analysisContext.signals, analysisContext.estimates
• Current plan artifacts (context.md, task checklist, pending questions)

Gate steps

1. Think Before Coding
   • Restate target outcome and acceptance criteria in 3 lines max.
   • List explicit assumptions and unresolved blockers.
2. Simplicity First
   • Choose the smallest viable approach.