claude

delegation-assistant

Breaks a project into chunks and matches each one to a team member on purpose -- by stated skill level, growth fit, and current workload -- instead of defaulting to whoever is most senior or most available. Keeps a roster, flags chunks nobody is ready for, and tracks how assignments actually went.

0 on GitHubby Meagan Wallerv0.2.0BlueOak-1.0.0updated 1 month agopeople-management
/

Plugin delegation-assistant from marketplace tech-leadership in meaganewaller/tech-leadership-marketplace. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (3)

  • delegation-log

    Records how a delegated assignment actually went -- finished as expected, needed more support than planned, or turned out to be a good stretch -- at ~/.tech-leadership/delegation/log.json, so later plans match better instead of repeating the same guesses. Use this skill when the user says "log how t

  • delegation-plan

    Breaks a project or big task into chunks and proposes an owner for each one deliberately -- by stated skill level, growth fit, and current workload -- rather than defaulting to the most senior or the most available person. Use this skill when the user says "help me split this up," "who should work o

  • delegation-roster

    Maintains the team roster used for delegation -- each person's skill areas with a stated level, growth interests they have said out loud, and current workload -- at ~/.tech-leadership/delegation/roster.json. Use this skill when the user says "set up my team roster," "add [name] to the roster," "upda

View source on GitHub

More from meaganewaller/tech-leadership-marketplace

All 7 plugins →

Checks a design doc for structural and completeness gaps before it goes to the team -- whether the problem statement is clear, real alternatives were weighed, failure modes and blast radius are addressed, rollout and rollback are planned, and ownership is named. Produces a findings table with draft questions to raise, not a line edit, and tracks which gaps keep recurring across a team's docs.

3 skills

0

Structures a blameless postmortem fast while details are still fresh -- capturing an incident timeline live, turning it into a full postmortem whose root causes are framed as system and process gaps rather than individual mistakes, and tracking recurring causes and never-closed action items across incidents.

3 skills

0

Prepares for 1:1s with direct reports by pulling recent PR/ticket activity and prior 1:1 history into talking points that go beyond status updates, then logs what was discussed and tracks follow-ups and themes over time.

3 skills

0

Rewrites a technical update -- a PR summary, an incident, an architecture decision, a sprint status -- for a specific non-technical audience, reframing it around business impact, risk, timeline, and cost without letting severity, uncertainty, or real caveats get smoothed away in the process. Keeps a profile of what each stakeholder cares about and a record of what they have already been told.

3 skills

0

Ranks technical debt by business impact rather than by how unpleasant the code is -- scoring blast radius, velocity drag, customer impact, cost of delay, and effort into a tiered Now/Next/Later list, then keeping a team-visible register and reporting on what actually gets paid down.

3 skills

0

TEMPLATE -- not a real plugin. Scaffolding used to validate the marketplace structure and all four tool adapters end to end. Copy this directory when starting a new plugin; don't install it as-is.

1 skill

0

Similar plugins

agents-md

claude

AGENTS.md as project instructions, by one option. Under claude-md-or-agents-md a project with no instruction files of its own gets its AGENTS.md files instead: a prompt.context hook asks $.fs.ancestors for every AGENTS.md and .claude/AGENTS.md from the filesystem root down to the working directory and hands them to the engine as project instruction files, which it renders, announces and withholds from agents exactly as it does CLAUDE.md, skipping any file the engine already loaded by import or link; a tool.call hook on Read attaches the ones under the project root as the engine attaches a nested CLAUDE.md. Under claude-md-and-agents-md every AGENTS.md is loaded beside CLAUDE.md. Under managed-only the project's and the person's instruction files are dropped and the organization's managed ones kept. Under claude-md the engine's walk stands alone. claude-md-or-agents-md is the default.

anthropics/claude-code 155,476

Tenant-isolated AI teams that plan work, coordinate tasks, recall approved context, and return evidence-backed results

6 skills · 6 commands · 4 agents · 1 MCP server

ruvnet/ruflo 81,589

data

claude

Data engineering for Apache Airflow and Astronomer. Author DAGs with best practices, debug pipeline failures, trace data lineage, profile tables, migrate Airflow 2 to 3, and manage local and cloud deployments.

35 skills · hooks

anthropics/claude-plugins-official 47,076

agent-teams

claudecodex

Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams

6 skills · 7 commands · 4 agents

wshobson/agents 42,461

Claude Code native multi-agent orchestration with intelligent model routing across agents and skills. Zero learning curve. Maximum power.

85 skills · 20 commands · 19 agents · 1 MCP server · hooks

Yeachan-Heo/oh-my-claudecode 40,800

Maintain delegation-assistant?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins7 plugins