Leadership review
Skill agent-packs/registry/plugins/eng-leader-workflows/.claude-plugin/skills/leadership-review
Run evidence-based engineering leadership reviews across strategy, portfolio and capacity, delivery, quality, architecture, launch readiness, security risk, AI-assisted engineering adoption, organizational health, and follow-through.From its SKILL.md
npx -y skills add agent-packs/registry --skill leadership-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.1 KB, 507 tokens by cl100k_base, as published. Nobody here has run it
Leadership Review
Use this workflow when an engineering leader needs a concise, decision-oriented review of an initiative, portfolio, team operating rhythm, launch, AI-assisted engineering rollout, or delivery risk.
Lead with the decision or risk that needs attention. Separate facts, assumptions, evidence confidence, risks, decisions, owners, dates, and follow-up actions. Do not turn activity measures into individual productivity scores.
Select The Review Cadence
- Use a weekly review for flow, blockers, near-term risks, and owner/date actions.
- Use a monthly review for trends, operational health, portfolio drift, dependencies, and capacity.
- Use a quarterly review for strategy, investment allocation, organization design, and stop-or-defer decisions.
Review Shape
-
Frame the decision.
- State the expected business or customer outcome, decision owner, deadline, and why the decision matters now.
- Name non-goals and constraints.
-
Assess evidence and confidence.
- Separate observed facts, reported signals, and assumptions.
- Rate confidence in decision-critical evidence and state what would change the recommendation.
- Prefer trends and system outcomes over isolated snapshots or activity counts.
-
Review execution and operating health.
- Assess delivery confidence, quality, reliability, security/privacy, performance, operational readiness, customer impact, and support burden.
- Identify the limiting constraint and any hidden operational or interruption work.
-
Reconcile portfolio and capacity.
- Compare committed work with actual capacity and cross-team dependencies.
- Recommend what to continue, accelerate, reshape, defer, or stop.
- Make every tradeoff and displaced investment explicit.
-
Make the decision.
- Compare viable options, including reversibility, blast radius, and cost of delay.
- Identify the decision maker and distinguish reversible from difficult-to-reverse choices.
- Capture the result in a decision log with rationale and review trigger.
-
Secure follow-through.
- Convert the decision into owner/date actions with evidence of completion.
- Record risks with likelihood, impact, mitigation, owner, and trigger.
- Set the next review date and the signals that should cause earlier escalation.
Output Contract
Return:
- a concise executive summary led by the decision or highest-severity risk;
- an evidence and confidence table;
- options, recommendation, and explicit tradeoffs;
- a decision log and risk register;
- a follow-through table with owner, due date, completion evidence, and review trigger.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.