```markdown
## Summary

[2-3 sentence overview of what the PR does and why]

## Changes

Key changes:
- [Specific change with rationale]
- [Specific change with rationale]

Files changed:
- `path/to/file.ext` - [What changed and why]

## Motivation

[Problem solved or requirement fulfilled]

## Implementation Details

[Key decisions and tradeoffs]

## Related

- Issue: [reference if applicable]
- Plan: `plans/...` [if applicable]
- Design doc: `docs/...` [if applicable]
- Depends on: [PR or issue]
- Blocks: [PR or issue]

## Testing

Automated:
- [ ] [Command or suite]

Manual:
- [ ] [Verification step]

## Breaking Changes

[List them, or state none]

## Security Considerations

[List them, or state none]

## Performance Impact

[List them, or state none]

## Rollout Plan

[If needed]

## Follow-up Work

- [ ] [Follow-up]

## Reviewer Notes

[What reviewers should focus on]
```