Appearance
Executive summary
This example proposes a concise handoff format that puts the requested decision, evidence, and next step before implementation detail. The goal is to reduce reviewer effort without creating a second tracking system.
Context
Reviewers often receive a link without enough context to know what needs attention. A short, consistent brief can make the first screen useful on a phone while keeping the source repository authoritative.
Proposed approach
Use a summary, review ask, change or option list, evidence, risks, and next step. Keep implementation details in the source pull request.
Options and trade-offs
| Option | Benefits | Costs or risks |
|---|---|---|
| Short structured brief | Faster scanning; explicit decision | Requires a small authoring habit |
| Free-form notes | Flexible | Review asks and evidence can be hard to find |
Milestones
- [ ] Try the format on one sanitized review item.
- [ ] Collect reviewer feedback and revise the template.
Risks and open questions
- Risk: repeated information can become stale. Keep source links canonical.
- Open question: which fields can remain optional for small changes?
Evidence and next step
No effectiveness claim is made in this sample. After approval, the example team can try the template on one review and record friction in the pull request.