Skip to content
Skillpedia
Tasks & projects40k · #5191

impediment-prioritization

Helps your agent organize and rank problems. It assesses value, cost, ease, and risk to prioritize what to do first.

What it does

This tool organizes a list of problems and their solutions. It uses a scoring system to determine what's most important to fix first, considering return, cost, ease, and risk.

When to use it

  • ✓When you have a list of problems and want to know which one to tackle first.
  • ✓When you need to organize tasks or risks by importance.
  • ✓When you want to compare different solutions for the same problem.

Example of what to ask your AI

“Prioritize these problems: 'Slow website', 'Missing social login', 'Payment error'. My solutions are: 'Optimize database', 'Implement Google login', 'Fix checkout bug'.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/github/awesome-copilot/blob/main/skills/impediment-prioritization/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/github/awesome-copilot/blob/main/skills/impediment-prioritization/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool evaluates each solution based on how much benefit it brings (ROI), how much it costs to implement, how easy it is to do, and the risk involved. It then uses a formula to calculate a final score and rank the items.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add github/awesome-copilot --skill impediment-prioritization

Or download just the file:

curl -L https://raw.githubusercontent.com/github/awesome-copilot/main/skills/impediment-prioritization/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Impediment Prioritization Skill

A domain-agnostic skill for ranking impediments and their countermeasures. Works with any {impediment, countermeasure} list — GHQR findings, audit results, retro action items, risk registers, architecture review gaps, etc.

When to Activate

Activate when the user:

  • Asks to prioritize, rank, sequence, or triage impediments, gaps, risks, findings, or remediation items
  • Provides a list of impediments with proposed countermeasures (or asks you to propose countermeasures for a list of problems)
  • Asks "what should we fix first" on any improvement / remediation backlog
  • Mentions value-stream prioritization, A3 countermeasures, ROI-vs-effort, or lean impediment ranking

Inputs

Accepted input: a list of {impediment, countermeasure} pairs. Sources include (non-exhaustive):

Source Maps to Impediment Maps to Countermeasure
GHQR / health-check findings Finding or gap (Status ≠ Expected) Recommendation / expected value
Audit results Non-conformance Remediation action
Retrospective "What went wrong" item Agreed improvement
Risk register Risk Mitigation
Architecture review Gap vs. target state Proposed change
User free-form list Problem statement Proposed fix

Rules:

  • One countermeasure per impediment. If the input suggests multiple remediation paths, select the primary one and note alternatives in the rationale — do not emit multiple rows for the same impediment.
  • Collapse duplicates before scoring.
  • If a source link / citation is available, attach it to the countermeasure.
  • If a confidence level is available on the source, surface it as an optional Confidence column.

Scoring Rubric (1–10 scales)

Score each impediment's countermeasure against all four criteria. See references/scoring-rubric.md for anchoring examples at the 1 / 5 / 10 levels across multiple domains (platform engineering, security, SRE, application development, governance).

Criterion Scale Definition
Return on Investment (ROI) 1 = low, 10 = high Efficiency gain delivered by the countermeasure to this step AND to the overall value stream. Not purely financial — weight throughput, cycle-time reduction, defect removal, user / developer experience, and compliance lift.
Cost to Implement 1 = inexpensive, 10 = very expensive Human capital (salary + time of people needed) plus any purchases, licenses, or infrastructure required to implement the countermeasure.
Ease of Deployment 1 = extremely hard, 10 = very easy Remediation effort required to actually deploy the countermeasure end-to-end. Reflects technical complexity, change-management burden, and rollback risk.
Risk Factor 1 = low risk, 10 = very high risk Risk weighted on impact to the overall value stream if the countermeasure goes wrong, stalls, or is deferred.

Every score must be accompanied by a one-line rationale. When a score is an estimate rather than drawn from explicit data, mark the rationale with (estimated).

Formula

Priority = ((ROI * (10 / Cost)) + (Ease * (10 / Risk))) / 2
  • Theoretical range: 1 → 100. Practical range on typical backlogs: ~1 → 100.
  • The scale minimum of 1 guarantees Cost and Risk are never zero (no divide-by-zero).
  • Higher Priority = do first.
  • Boundary checks:
    • ROI=10, Cost=1, Ease=10, Risk=1 → ((10*10)+(10*10))/2 = 100
    • ROI=1, Cost=10, Ease=1, Risk=10 → ((1*1)+(1*1))/2 = 1

Use the formula verbatim. Do not reweight, normalize, or substitute.

Method (agent procedure)

  1. Ingest the impediment list. Confirm 1:1 impediment-to-countermeasure mapping; collapse duplicates.
  2. Confirm the countermeasure for each impediment. Prefer documented best practice for the domain. Cite a public / authoritative link when one is available.
  3. Score all four criteria using the rubric. Write a one-line rationale per criterion.
  4. Compute Priority using the formula. Round to one decimal place.
  5. Sort rows by Priority descending. Assign Rank starting at 1.
  6. Render the output table (see below).
  7. Call out the top 3 impediments with a short "why act first" paragraph.

…

FAQ

What are 'impediments' and 'countermeasures'?

'Impediments' are the problems or obstacles. 'Countermeasures' are the solutions or actions to resolve those problems.

How is the score calculated?

The score uses a formula that combines Return on Investment (ROI) and Ease of Implementation, divided by Cost and Risk, respectively. The exact formula is `((ROI * (10/Cost)) + (Ease * (10/Risk))) / 2`.

Can I use this for any type of list?

Yes, the tool is domain-agnostic and can be used to organize lists of problems from any area, such as audit findings, retrospective items, risks, or any task list.

Details

Original description by the author

Ranks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritization formula. Use when someone asks to prioritize, rank, sequence, or triage impediments, countermeasures, remediation items, risks, findings, gaps, action items, or backlog entries; or mentions value-stream prioritization, A3 /

repo: github/awesome-copilot

Popularity

GitHub stars
40k
Ranking position
#5191
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills