PM triage: separate portfolio ranking scope from repo-local execution #839

New issue

Closed

opened 2026-08-01 17:05:35 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-01 17:05:35 +00:00

Owner

Outcome

Teach the PM priority model to resolve an explicit ranking pool before assigning P0-P4 while preserving repository ownership for executable work.

Acceptance criteria

One repository remains the default ranking pool.
An organization-profile declaration may define an organization-wide pool.
The global percentile cut runs once across that resolved pool.
Executable issues, labels, readiness, dependencies, and milestones remain in the owning repository.
The composed-skill and documentation validators pass.

Context

Forgejo milestones are repository-local. Coilyco Gaming needs portfolio-level Eco prioritization without duplicating work into a central tracker.

## Outcome Teach the PM priority model to resolve an explicit ranking pool before assigning P0-P4 while preserving repository ownership for executable work. ## Acceptance criteria - [ ] One repository remains the default ranking pool. - [ ] An organization-profile declaration may define an organization-wide pool. - [ ] The global percentile cut runs once across that resolved pool. - [ ] Executable issues, labels, readiness, dependencies, and milestones remain in the owning repository. - [ ] The composed-skill and documentation validators pass. ## Context Forgejo milestones are repository-local. Coilyco Gaming needs portfolio-level Eco prioritization without duplicating work into a central tracker.

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-01 17:05:35 +00:00

coilyco-ops referenced this issue from a commit

2026-08-01 17:06:36 +00:00

docs(pm): resolve org-wide priority pools (closes #839)

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-01 17:06:56 +00:00

docs(pm): resolve org-wide priority pools #840