Explain Change

Produce an evidence-backed change briefing. Organize it around behavior, decisions, and an acceptance-level mental model.

Success Criteria

Finish when the user can explain the change and make the requested next decision from supported facts, visible tradeoffs, and clearly named unknowns.

Authority

Use this order:

1. Repository guidance and documented project intent.
2. The original request, accepted plan, issue, ADR, and settled decisions.
3. The actual diff, current code, directly affected consumers, and tests.
4. PR descriptions, commit messages, and handoffs as claims to verify.