This is great and I would really put emphasis on this! (see suggestions next comment)

might be helpful to clarify here that protocols are mandatory steps that must always be followed and demonstrated, while guidelines are best-practice suggestions meant to improve quality but not strictly required

This is a very strong list in my opinion! Two suggestions: - slightly differentiate “step-by-step explanation of the code” from “plain-language explanation,” since they can overlap (do we mean technical explanation vs high level rationale behind the code?) - maybe add a point on error handling expectations? for example, how the code responds to invalid or missing data

One improvement here could be to ask Copilot to evaluate the code incrementally and at execution level (at runtime), that is to evaluate the code based on how it actually runs, not just how it looks or reads. For example, verifying assumptions about inputs/outputs and testing components in isolation to prevent that individual errors/failures trigger cascading error that are very difficult to debug