RA-06
Cross-Skill Dependency — Person Is Only Assignee for a Skill Area
Resource Allocation
Default severity: medium
ProcessOutputRiskEffort
What it detects
One person is the sole assignee across all issues tagged with a specific component, label, or technology area — no other team member has logged work or been assigned in that domain. The team has a single point of knowledge: if that person is unavailable, that skill area stops entirely.
Detection formula
skill_areas = config.ra.skill_area_fields // e.g. component, label, epic-label, custom field FOR each_skill_area S: assignees(S) = DISTINCT(assignees, issues WHERE skill_area=S) worklog_authors(S) = DISTINCT(worklog.author, issues WHERE skill_area=S) all_involved(S) = UNION(assignees(S), worklog_authors(S)) IF COUNT(all_involved(S)) = 1 THEN FLAG single_skill_owner IF COUNT(assignees(S)) = 1 AND COUNT(worklog_authors(S)) = 1 AND same person THEN CRITICAL — true knowledge silo Report: skill_area, sole_owner, issues_in_area, last_activity_date, risk_if_unavailableExamples in practice
- One person owns a disproportionate share of critical-path or high-WIP work.
- Delivery risk rises when a single expert becomes the throughput bottleneck.
- A team shows one person is the sole assignee across all issues tagged with a specific component, label, or technology area while skill area fields is set to \[\'component\',\'label\'\].
Suggested response
Reduce single points of failure—spread critical skills and lighten overloaded contributors.
Coaching playbook
Symptom
One person is the sole assignee across all issues tagged with a specific component, label, or technology area — no other team member has logged work or been assigned in that domain. The team has a single point of knowledge: if that person is unavailable, that skill area stops entirely.
Why it matters
When "Cross-Skill Dependency — Person Is Only Assignee for a Skill Area" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Reduce single points of failure—spread critical skills and lighten overloaded contributors.
Facilitation questions
- What system change would stop "Cross-Skill Dependency — Person Is Only Assignee for a Skill Area" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.