# PR Template

Use this as the starting point for `.submissions/<change-slug>.pr.md`, where `<change-slug>` comes from the task title.

The PR title should be a polished version of the task title so the task, branch, PR, and submission artifact remain easy to correlate.

```md
## Summary
- <one-line statement of the user-visible or developer-visible outcome>
- <key implementation choice>
- <artifact/report created>

## Changes
- <changed area 1>
- <changed area 2>
- <changed area 3>

## How It Fits
- <where the change sits in the codebase>
- <upstream/downstream relationships>

## Validation
- `<command>` — pass/fail/not configured
- `<command>` — pass/fail/not configured
- Manual: <what was verified>

## Risks / Follow-Ups
- <risk or caveat>
- <future improvement>

## Submission Artifact
- `.submissions/<change-slug>.html`
```

Keep the PR body shorter than the HTML report. The report is the full reviewer packet.