leadership

Plugin leadership from marketplace metapowers in bromso/metapowers. Commands read from the repo's manifest — 18 days ago.

Skills (11)

• assess

  Assess your leadership style, each team member's maturity and the team's current challenges, and recommend what to tackle first. Use when the user is new to leading a team or has inherited one and wants to know where to start as its leader. Not for a health check of a delivery team; see /project-man

• conflict

  Resolve a conflict between team members by mapping each side's interests, finding the root cause and planning a facilitated conversation with ground rules and follow-up. Use when two people on the user's team keep clashing, or a disagreement is hurting the team's work.

• decision

  Make a structured leadership decision — choose whether to decide alone, consult, delegate or seek consensus, compare options by risk and reversibility, and recommend one with a rollback plan. Use when the user is torn between options on a team or management call and wants a clear way to decide.

• delegate

  Delegate one task well — pick the right person by skill, growth and workload, then define the deliverable, their authority, support, check-ins and done criteria. Use when the user has a task to hand off and wants to decide who should own it and how to brief them.

• develop

  Create quarterly team OKRs plus an individual growth plan for each team member, with a weekly, monthly and quarterly feedback cadence. Use when the user wants to plan how each person on their team will grow this quarter alongside the team's goals. Not for writing OKRs on their own; see /leadership:o

• feedback

  Prepare feedback for one person using Situation-Behavior-Impact, with feedforward, an opening line and how to handle likely reactions. Use when the user needs to give a team member praise or constructive feedback about something specific they did.

• okrs

  Set or review OKRs for a team or individual — 2-3 objectives with measurable key results, baselines and targets, aligned upward, with explicit trade-offs. Use when the user needs to write next quarter's OKRs or check whether existing ones measure outcomes rather than activities. Not for per-person g

• one-on-one

  Prepare the agenda for a 1:1 meeting with a team member — check-in prompts, space for their topics, progress, growth goals and any feedback to deliver. Use when the user has an upcoming 1:1 with someone they manage and wants talking points for it.

• retro

  Facilitate a team retrospective in Start/Stop/Continue format on how the team works together, digging into root causes and recurring patterns and ending with owned actions. Use when a leader wants to reflect with their team on a period, project or rough patch to improve how they work. Not for a spri

• sustain

  Establish ongoing leadership rituals — weekly 1:1s, biweekly retros, monthly reviews and quarterly OKR resets — plus a leader's playbook and team health metrics. Use when the user's team is set up and they want a recurring operating rhythm that keeps it healthy without burning themselves out.

• vision

  Define a team's purpose, 3-5 values with concrete behaviors, and the target culture for decisions, communication and conflict. Use when the user wants to articulate what their team stands for, write team values, or reset the team's culture.

Hooks (1)

• PreToolUse

  "${CLAUDE_PLUGIN_ROOT}"/hooks/phase-gate.sh

Similar plugins