From 1520b859e5889675e2ea057164499fdaad955361 Mon Sep 17 00:00:00 2001
From: Vadim Zolotokrylin <1125014+zolotokrylin@users.noreply.github.com>
Date: Thu, 30 Jul 2026 11:44:36 +0800
Subject: [PATCH] docs(rules): take the highest ranked Goal your lead gives you

---
 docs/rules/DEV-110.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/rules/DEV-110.md b/docs/rules/DEV-110.md
index dc89924..9970dce 100644
--- a/docs/rules/DEV-110.md
+++ b/docs/rules/DEV-110.md
@@ -15,8 +15,12 @@ Effort is unanchored, and no one can tell what it is meant to achieve.
 
 Every contribution begins from a Goal issue, with a clear owner.
 
-1. Find a Goal by filtering the repo's issues for the `Goal:` prefix. Prioritize
-   by impact and urgency; consult your lead if unsure which to take.
+1. Where your lead gives you a ranked order of your Goals, take the highest one
+   still open. That order decides what you work on next; do not re-rank it, and
+   raise it with your lead when it is unclear or cannot be met.
+1. Otherwise find a Goal by filtering the repo's issues for the `Goal:` prefix,
+   prioritize by impact and urgency, and consult your lead if unsure which to
+   take.
 1. Assign yourself, or get assigned, so ownership is unambiguous.
 
 A Goal follows the pattern `Goal: [statement]` and must link a Spec; a Goal is