Balances team workload and issue distribution for Todo-vibe based on capacity.
Install
mkdir -p .claude/skills/assign && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19026" && unzip -o skill.zip -d .claude/skills/assign && rm skill.zipInstalls to .claude/skills/assign
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Rebalance workload across the Todo-vibe team. Redistributes unassigned or over-capacity issues respecting the ownership map and current load. Use when someone is OOO, a sprint is overloaded, or asked to rebalance/reassign work.Key capabilities
- →Redistribute issues from overloaded team members
- →Assign unassigned sprint-ready issues
- →Reassign open issues for out-of-office team members
- →Propose reassignments based on ownership and capacity
- →Apply reassignments using owner labels
- →Output a rebalancing summary with before and after loads
How it works
The skill fetches current open issues and calculates each team member's load based on assigned issues, weights, and sprint capacity. It then executes a selected mode to rebalance, assign unassigned, or reassign issues for out-of-office members.
Inputs & outputs
When to use assign
- →Rebalance sprint workload
- →Assign unassigned issues
- →Adjust for out-of-office team members
About this skill
You are rebalancing workload for the Todo-vibe project (repo: AntHanna23/Todo-vibe).
Refer to .claude/skills/TEAM.md for the team roster, ownership map, and sprint capacity.
Modes
The skill operates in one of these modes based on $ARGUMENTS:
rebalance(default) — find overloaded team members and redistribute their excess issues<name>— show that person's current load and suggest what to moveunassigned— assign all unassigned sprint-ready issues to the right ownerooo <name>— person is out of office, redistribute all their open issues
Process
Step 1 — Fetch current state
gh issue list --repo AntHanna23/Todo-vibe --state open \
--json number,title,labels,assignees,milestone,body --limit 100
Step 2 — Build load map
For each team member, calculate:
- Issues assigned + their weights (extract
Weight: <n>from body) - Remaining capacity = sprint capacity (from TEAM.md) − assigned weight
- Load % = assigned weight / sprint capacity × 100
Step 3 — Execute the selected mode
rebalance mode:
- Identify anyone over 100% capacity
- For each overloaded person, find their lowest-priority issues (p3 first, then p2)
- Find the team member with the most remaining capacity who owns the same area (per TEAM.md ownership map)
- Propose the reassignment
<name> mode:
- Show that person's full issue list with weights
- Show their capacity utilization
- Suggest 1–2 issues they could hand off if over capacity, or flag if under-loaded
unassigned mode:
- Find all open issues with no assignee
- For each, determine the correct owner from the area labels and TEAM.md ownership map
- Assign them
ooo <name> mode:
- Find all open issues assigned to that person
- For each issue, find the best available team member based on: area ownership → remaining capacity → priority (p0/p1 first)
- Reassign all of them
Step 4 — Apply reassignments
For each reassignment, confirm the action before applying (list all changes first):
Proposed reassignments:
#<n> — <title>: <from> → <to> (reason: <over capacity / unassigned / OOO>)
#<n> — <title>: <from> → <to>
...
Then apply using owner labels (this project does NOT use GitHub assignees):
# Add new owner label
gh issue edit <number> --repo AntHanna23/Todo-vibe --add-label "owner: <handle>"
# Remove old owner label
gh issue edit <number> --repo AntHanna23/Todo-vibe --remove-label "owner: <old-handle>"
Step 5 — Output the rebalancing summary
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Workload Rebalancing — <today's date>
Mode: <mode>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
BEFORE
─────────────────────────────────────
Riley Chen: <w> / 12 pts (<load>%) <🔴 over / 🟡 at capacity / 🟢 ok>
Sam Patel: <w> / 10 pts (<load>%)
Morgan Rivera: <w> / 10 pts (<load>%)
Casey Morgan: <w> / 10 pts (<load>%)
Jordan Blake: <w> / 8 pts (<load>%)
Anthony Hanna: <w> / 10 pts (<load>%)
Unassigned: <w> pts across <n> issues
CHANGES MADE
─────────────────────────────────────
#<n> — <title>
<from> → <to>
Reason: <over capacity / unassigned / OOO / area ownership>
AFTER
─────────────────────────────────────
Riley Chen: <w> / 12 pts (<load>%)
... (updated totals)
⚠️ UNRESOLVABLE
─────────────────────────────────────
#<n> — <title>: <why it couldn't be reassigned, e.g. "all area owners at capacity">
Notes
- Never reassign p0 issues without flagging Jordan Blake (Tech Lead) — add a comment
- Prefer reassigning to the canonical area owner (TEAM.md ownership map) over anyone with spare capacity
- If no canonical owner has capacity, escalate to Jordan Blake
- Do not reassign issues that are
status: in-progress— flag them instead
Mode / person: $ARGUMENTS
When not to use it
- →When the project is not AntHanna23/Todo-vibe
- →When the team roster, ownership map, or sprint capacity are not defined in .claude/skills/TEAM.md
- →When reassigning p0 issues without flagging Jordan Blake
Limitations
- →Does not reassign p0 issues without flagging Jordan Blake
- →Does not reassign issues that are status: in-progress
- →Requires team roster, ownership map, and sprint capacity to be defined in .claude/skills/TEAM.md
How it compares
This skill automates the calculation of team load and proposes/applies reassignments based on predefined rules and team data, unlike manual issue management.
Compared to similar skills
assign side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| assign (this skill) | 0 | 3mo | Review | Intermediate |
| planning-with-files | 233 | 6mo | Review | Intermediate |
| trello | 41 | 2mo | Review | Beginner |
| pmbok-project-management | 38 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
planning-with-files
davila7
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
trello
openclaw
Manage Trello boards, lists, and cards via the Trello REST API.
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
clickup
civitai
Interact with ClickUp tasks and documents - get task details, view comments, create and manage tasks, create and edit docs. Use when working with ClickUp task/doc URLs or IDs.
ma-playbook
alirezarezvani
M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.