Skip to content

docs(rules): take the highest ranked Goal your lead gives you #136

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zolotokrylin merged 1 commit into from
Jul 30, 2026
Merged

docs(rules): take the highest ranked Goal your lead gives you #136

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/rules/DEV-110.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading