diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e2a52f6..d326074 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -12,7 +12,7 @@ A specific repository may override this org-wide default with its own `CONTRIBUT
 
 ## Workflow
 
-1. Branch from the default branch using `<type>/<description>` (for example, `feat/add-widget`).
+1. Branch from the default branch, naming it `<type>/<short-description>` (for example, `feat/add-widget`) per the org's [branch-naming convention](https://github.com/melodic-software/standards/blob/main/conventions/engineering/naming.md#branch-names-type-prefix-then-a-behavior-naming-slug). A repository may gate the pattern locally, but no check enforces it by default, so treat it as a convention rather than a requirement.
 2. Make your change, with tests where applicable.
 3. Ensure the project builds and its checks pass locally.
 4. Open a pull request, fill out the template, and link the related issue. Title it using [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) with one of the standard types — `<type>[optional scope]: <description>`, for example `feat(api): add pagination`. The title becomes the squash-merge commit subject on the default branch. Where the repository enforces this, a `pr-title` check reports on your pull request and must pass before merge.