Implementation Preflight
Use this preflight when uncertainty could change the implementation, not as a ceremony before every edit.
- Resolve facts from the repository and current conversation first. State only assumptions that affect the outcome; ask about choices evidence cannot settle.
- Identify the observable result and how to verify it. For dependent work, give a short plan whose steps lead to that result.
- Use nwiizo-coding-style for implementation choices, reuse, simplification boundaries, and verification. Keep this preflight focused on unresolved assumptions and the observable result.
- Once the necessary choices are resolved, continue authorized implementation. Do not ask for another approval of the plan or repeat settled discovery.
A small diff is useful when it remains clear and correct. Do not replace engineering judgment with a line count or a fixed number of questions.
Adapted from Karpathy's observations, andrej-karpathy-skills.