Explain Like

Explain code changes or design documents at three progressive expertise levels to ensure understanding and catch logical gaps.

When to Use

1. PR/Branch Explanations: After completing work, explain changes to verify clarity
2. Design Validation: After writing a design doc, explain it back to catch missing pieces

Both workflows serve knowledge transfer - helping others (or your future self) understand complex changes.

Workflow

1. Determine the subject:
   • Branch/PR changes? → Gather commits and diffs from git
   • Design document? → Read the specified design file