Agent skill · Security

impediment-prioritization

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 / lean countermeasure ranking, ROI vs. effort scoring, or building a remediation / improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill impediment-prioritization --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Version: 2.0.0
Declared author: ajenns
Path: skills/impediment-prioritization/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 | |

What's inside
Steps it walks through
  1. When to Activate
  2. Inputs
  3. Scoring Rubric (1–10 scales)
  4. Formula
  5. Method (agent procedure)
  6. Output Template
  7. Assumptions & Guardrails
  8. Downstream Integration (optional)
Ships with 1 file
  • references/scoring-rubric.md
More from awesome-copilot
All skills →
About this skill
What does the impediment-prioritization skill do?

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 / lean countermeasure ranking, ROI vs. effort scoring, or building a remediation / improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture

How do I install it?

Run `npx skills add github/awesome-copilot --skill impediment-prioritization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going