@@ -15,7 +15,7 @@ If the repository-relative guide is unavailable from an installed plugin, read i
 
 ## Agent-specific contract
 
-- Read the target repository's instructions and PR template before editing its metadata.
+- Read the target repository's instructions and linked evergreen documentation before editing PR metadata.
 - Apply the guide's authoring and replay checks to the full delivered range.
 - Report the edited PR URL, relevant baseline, verified impact, and validation outcomes to the owning session.
 - Stop and report when the cited guidance or required source evidence is unavailable; identify the evidence gap.
@@ -67,7 +67,6 @@ The current template's default repository anatomy is:
 │   │   ├── .powershell-psscriptanalyzer.psd1
 │   │   └── .textlintrc
 │   ├── PSModule.yml
-│   ├── pull_request_template.md
 │   ├── release.yml
 │   ├── workflows/
 │       └── Process-PSModule.yml
@@ -107,7 +106,7 @@ Treat files and directories as follows:
   Preserve its intent and only migrate paths when the framework contract
   requires it.
 - `.github/PSModule.yml`, linters, Dependabot, CODEOWNERS, release metadata,
-  pull-request templates, and repository guidance are configuration surfaces.
+  and repository guidance are configuration surfaces.
   Inspect and preserve them independently of the caller workflow.
 - `tests/BeforeAll.ps1` and `tests/AfterAll.ps1` are optional root-level
   module-local phases, not recursively discovered test files.
 
@@ -14,10 +14,9 @@ the description as the release notes body. The release name is the resolved vers
 `Publish.Module.UsePRTitleAsReleaseName` changes that setting. This guide governs authoring; it does not change the
 publisher, version resolver, label mappings, or release-note settings.
 
-Use the [MSX PR format](https://msx.no/docs/Ways-of-Working/PR-Format/) for titles and description structure, and the
-[repository template](https://github.com/PSModule/Process-PSModule/blob/main/.github/PULL_REQUEST_TEMPLATE.md) as the
-local starting point. The guidance applies to PowerShell modules, reusable workflows, GitHub Actions, libraries,
-services, infrastructure modules, and published guidance.
+Use the [MSX PR format](https://msx.no/docs/Ways-of-Working/PR-Format/) for titles and description structure.
+Write the record directly in the pull request using its in-document examples. The guidance applies to PowerShell
+modules, reusable workflows, GitHub Actions, libraries, services, infrastructure modules, and published guidance.
 
 ## Release records and evergreen documentation
 
 
@@ -92,7 +92,6 @@ Module repositories use the PSModule framework layout:
 | `.github/linters/` | Linter configuration used by the framework's linting stage, including `.markdown-lint.yml` and `.powershell-psscriptanalyzer.psd1`. |
 | `.github/dependabot.yml` | Configures ecosystem-appropriate dependency-update pull requests. For PowerShell module repositories the `github-actions` ecosystem is expected; add any other ecosystems the module actually develops in. |
 | `.github/CODEOWNERS` | Ownership routing for reviews and protected areas. |
-| `.github/pull_request_template.md` | Scaffolds audience-first titles and classified results with scoped upgrade instructions and evidence; see [Formatting release-note pull requests](../guides/formatting-release-note-prs.md). |
 | `.gitattributes` | Normalizes line endings and declares text/binary handling so the module can be developed and built consistently on Linux, macOS, and Windows. |
 | `.gitignore` | Ignores files that must never be committed, tailored to the PowerShell-module ecosystem: operating-system files, editor and developer-tooling files, PowerShell and Pester test-harness artifacts, and all local build outputs and files created during build and test. |
 | `src/` | Module source compiled into the shipped artifact. |
@@ -107,6 +106,8 @@ Module repositories use the PSModule framework layout:
 | `icon/` | Module icon assets. |
 
 Detailed source layout rules live in [PowerShell module standard](powershell-module-standard.md#repository-layout).
+Pull request authoring follows [Formatting release-note pull requests](../guides/formatting-release-note-prs.md),
+which applies the canonical [MSX PR format](https://msx.no/docs/Ways-of-Working/PR-Format/).
 
 ### Caller workflow and reusable workflow
 
@@ -155,7 +156,6 @@ Required baseline files for module repositories:
 | `CLAUDE.md` | Claude Code entry point that imports `AGENTS.md`. |
 | `.github/dependabot.yml` | Configures ecosystem-appropriate dependency-update pull requests. For PowerShell module repositories the `github-actions` ecosystem is expected; add any other ecosystems the module actually develops in. |
 | `.github/CODEOWNERS` | Review routing for source, docs, and GitHub workflow files. |
-| `.github/pull_request_template.md` | Scaffolds audience-first titles and classified results with scoped upgrade instructions and evidence; see [Formatting release-note pull requests](../guides/formatting-release-note-prs.md). |
 | `.github/PSModule.yml` | Module workflow defaults and overrides. |
 | `.gitattributes` | Normalizes line endings and declares text/binary handling so the module can be developed and built consistently on Linux, macOS, and Windows. |
 | `.gitignore` | Ignores files that must never be committed, tailored to the PowerShell-module ecosystem: operating-system files, editor and developer-tooling files, PowerShell and Pester test-harness artifacts, and all local build outputs and files created during build and test. |