New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

80 20 Feature Prioritization

by hashgraph-online in hashgraph-online/awesome-codex-plugins

A skill your agent uses when scoping a roadmap, prioritizing features, planning an MVP, or deciding what to ship and what to defer.

Apache-2.0Auto-check passedProduct & Project Management

Install 80 20 Feature Prioritization

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill 80-20-feature-prioritization -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins 80-20-feature-prioritization --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/HDeibler/universal-design-principles/plugins/cognition-and-learnability-principles/skills/80-20-feature-prioritization .claude/skills/80-20-feature-prioritization && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
80-20-feature-prioritization
GitHub stars
1.3k
Token cost
~1.4k tokens
SKILL.md length
748 words
Files
2 (incl. references)
Skills in repo
716
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when scoping a roadmap, prioritizing features, planning an MVP, or deciding what to ship and what to defer.

  • Works in 4 steps: Usage signal → Value signal → Effort signal → …
  • Scoping a roadmap
  • SKILL.md covers The prioritization framework, Decision matrix, Roadmap shaping and When the 80/20 cut hurts, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

80 20 Feature Prioritization is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when scoping a roadmap, prioritizing features, planning an MVP, or deciding what to ship and what to defer. Trigger when the user asks "what should we build next?", "is this feature worth it?", "should we ship feature X?", or when reviewing a feature backlog. Sub-aspect of 80-20-rule; read that first.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/prioritization-frameworks.md`).

It sits in Product & Project Management, covering Prioritization frameworks. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

  • Scoping a roadmap
  • Prioritizing features
  • Planning an MVP
  • Deciding what to ship and what to defer

Example prompts

  • “what should we build next?”
  • “is this feature worth it?”
  • “should we ship feature X?”
  • “/80-20-feature-prioritization”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Usage signal
  2. Value signal
  3. Effort signal
  4. Strategic signal

What it can do on your machine

Read from SKILL.md and the folder at commit 3e1456a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

80 20 Feature Prioritization loads about 1.4k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 748 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 3e1456a, republished under its Apache-2.0 licence (© hashgraph-online). 748 words, ~1,409 tokens.

Download SKILL.mdSave it as .claude/skills/80-20-feature-prioritization/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
80-20-feature-prioritization
description
Use this skill when scoping a roadmap, prioritizing features, planning an MVP, or deciding what to ship and what to defer. Trigger when the user asks "what should we build next?", "is this feature worth it?", "should we ship feature X?", or when reviewing a feature backlog. Sub-aspect of `80-20-rule`; read that first.

80/20 in feature prioritization

The most direct application of the 80/20 rule: deciding which features to invest in. Most products accumulate features over time; many of those features see little use. The discipline is identifying the critical fraction worth deepening and the long tail worth either tucking or removing.

The prioritization framework

For each feature (proposed or existing), gather:

1. Usage signal

If the feature exists: how many users engage with it? How often? Is engagement growing or declining?

If the feature is proposed: how many users say they want it? Is that signal coming from a vocal minority or a representative sample?

2. Value signal

When the feature is used, how much value does it produce? A rarely-used feature that produces enormous value when used (year-end tax export) may be more important than a frequently-used one that produces marginal value (a counter widget).

3. Effort signal

What does it cost to build, maintain, support, and document?

4. Strategic signal

Does the feature reinforce a competitive position, retain a key customer segment, or enable future capabilities?

The 80/20 cut isn't pure usage — it weights usage by value. A rarely-used essential feature stays in the critical fraction. A frequently-used decorative one might not.

Decision matrix

A simple 2×2 to organize:

                    Low value          High value
                    ───────────         ──────────
Low effort     │  Cleanup later   │   Ship now
High effort    │  Don't build     │   Major investment

The tricky cases are the diagonals: low-effort + low-value tasks accumulate as "death by a thousand cuts" if not pruned; high-effort + high-value tasks need ruthless scoping or they slip schedule.

Roadmap shaping

The 80/20 view of a roadmap:

  • The critical 20% of planned work should account for ~80% of expected user impact. If the planned work is spread evenly across many small features, you're probably underweighting the few that matter most.
  • The trailing 80% of planned work should be either skipped or radically scoped down.

A useful exercise: take a quarterly roadmap. For each item, estimate user impact and engineering effort. Sort by impact-per-effort. Cut the bottom half. The team's quarter is suddenly half the size with most of the impact preserved.

When the 80/20 cut hurts

  • Power-user retention. A feature only 5% of users touch may be the reason that 5% (often the highest-paying segment) chose your product.
  • Compliance and accessibility. Required by law or ethics; can't be dropped.
  • Foundational capability. A feature whose value is in enabling other features. Search isn't valuable in itself; it's valuable because it makes everything findable.
  • Trust signals. Audit logs, exportable data, account deletion. Rarely used directly but their presence reassures prospects.

These deserve a different evaluation than pure-usage 80/20 would suggest.

Show full SKILL.md (331 more words)Show less

Roadmap anti-patterns

  • The feature factory. Every quarter ships 10 features. Most are small. None move metrics. Time fragments across all of them.
  • The pet feature. A senior leader's favorite that doesn't show up in user research but ships every quarter.
  • The "and one more thing." A small tweak added to a major feature that doubles its scope.
  • The unfinished long tail. Features shipped but never polished, growing into a maintenance burden.
  • The roadmap by request. Building features customers asked for without checking whether they reflect underlying needs (often the underlying need is met by a different feature you already have).

Worked example: pruning a settings page

A SaaS product's settings page has 38 controls. Usage analytics:

  • 7 controls used by ≥50% of users monthly.
  • 14 used by 10–50%.
  • 17 used by <10%.

Of the trailing 17:

  • 5 are needed for compliance (audit log, data export, account deletion). Keep.
  • 4 are integrations with services the product team is winding down. Remove from settings; deprecate.
  • 8 are legacy options most users have never touched. Move to "Advanced" disclosure; review for removal in a future cycle.

Result: settings page now shows ~7+5 (12 controls) primary; 14 secondary; rest tucked. Maintenance burden drops; common use is faster.

Heuristics

  1. The "what does the data say?" check. Usage analytics before opinion. If the data isn't available, instrument first; decide later.
  2. The "who would scream?" test. For features in the trailing 80%, ask. Each scream is a candidate to retain (or relocate); silence is permission to cut.
  3. The "would we build this today?" test. For each existing feature, imagine you were starting fresh. Would you build it? If no, it's a candidate for deprecation.
  4. The retention attribution. Pair feature usage with retention/expansion data. Features used by retained users may be more valuable than raw usage suggests.
  • 80-20-rule (parent).
  • 80-20-redesign-targeting — the within-existing-product version of the same prioritization.
  • hicks-law — every feature is an option; cutting features cuts decision cost.
  • progressive-disclosure — alternative to cutting: tucking.

© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/HDeibler/universal-design-principles/plugins/cognition-and-learnability-principles/skills/80-20-feature-prioritization of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • references/prioritization-frameworks.md

Open the folder on GitHubat commit 3e1456a

Compare with similar skills

80 20 Feature Prioritization next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

80 20 Feature Prioritization compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
80 20 Feature Prioritization this skillhashgraph-online/awesome-codex-plugins1.3k—~1.4kAutomated safety check: PassApache-2.0
Agile Product Owneralirezarezvani/claude-skills28k3 repos~3.2kAutomated safety check: PassMIT
Prioritization Framework Advisordeanpeters/Product-Manager-Skills7.2k2 repos~4.2kAutomated safety check: PassCustom licence
Strategic Roadmap Planningdeanpeters/Product-Manager-Skills7.2k2 repos~4.7kAutomated safety check: PassCustom licence
Idea Validatoraakashg/pm-claude-skills112—~2.3kAutomated safety check: PassMIT
Triagejoa23/linear-cli144—~699Automated safety check: PassMIT

Similar skills

  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Product & Project ManagementAuto-check passed

  • Prioritization Framework Advisor

    deanpeters/Product-Manager-Skills

    Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.

    7.2k GitHub starsUsed in 2 repos~4.2k tokens
    Product & Project ManagementAuto-check passed

  • Strategic Roadmap Planning

    deanpeters/Product-Manager-Skills

    Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.

    7.2k GitHub starsUsed in 2 repos~4.7k tokens
    Product & Project ManagementAuto-check passed

  • Idea Validator

    aakashg/pm-claude-skills

    A skill your agent uses when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something.

    112 GitHub stars~2.3k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed

  • Triage

    joa23/linear-cli

    Triage and prioritize Linear backlog issues using the linear CLI.

    144 GitHub stars~699 tokensUpdated 26 days ago
    Product & Project ManagementAuto-check passed

  • Define Opportunity Tree

    product-on-purpose/pm-skills

    Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.

    716 GitHub stars~1.1k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 716 skills in this repo

  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed

  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Categories

Questions about 80 20 Feature Prioritization

What does 80 20 Feature Prioritization do?

A skill your agent uses when scoping a roadmap, prioritizing features, planning an MVP, or deciding what to ship and what to defer. 80 20 Feature Prioritization is an agent skill from hashgraph-online/awesome-codex-plugins. Use this skill when scoping a roadmap, prioritizing features, planning an MVP, or deciding what to ship and what to defer.

When should I use 80 20 Feature Prioritization?

80 20 Feature Prioritization fits situations like: scoping a roadmap; prioritizing features; planning an MVP; deciding what to ship and what to defer.

How do I install 80 20 Feature Prioritization in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill 80-20-feature-prioritization -a claude-code`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/cognition-and-learnability-principles/skills/80-20-feature-prioritization in hashgraph-online/awesome-codex-plugins) into .claude/skills/80-20-feature-prioritization in your project. Claude Code loads it when a task matches its description.

How do I install 80 20 Feature Prioritization in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill 80-20-feature-prioritization -a codex`. Or copy the skill folder (plugins/HDeibler/universal-design-principles/plugins/cognition-and-learnability-principles/skills/80-20-feature-prioritization in hashgraph-online/awesome-codex-plugins) into .agents/skills/80-20-feature-prioritization in your project. Codex loads it when a task matches its description.

Can I use 80 20 Feature Prioritization in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill 80-20-feature-prioritization -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/80-20-feature-prioritization, .gemini/skills/80-20-feature-prioritization, .github/skills/80-20-feature-prioritization and .opencode/skills/80-20-feature-prioritization in your project.

What does 80 20 Feature Prioritization need to run?

SKILL.md names no scripts, command-line tools or credentials: 80 20 Feature Prioritization is instructions for the agent only.

Does 80 20 Feature Prioritization access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is 80 20 Feature Prioritization safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does 80 20 Feature Prioritization use?

80 20 Feature Prioritization is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does 80 20 Feature Prioritization use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 581 tokens, read only when the agent opens those files.

What are the alternatives to 80 20 Feature Prioritization?

Skills that share tags, products or a category with 80 20 Feature Prioritization: Agile Product Owner (alirezarezvani/claude-skills, 28k stars), Prioritization Framework Advisor (deanpeters/Product-Manager-Skills, 7.2k stars), Strategic Roadmap Planning (deanpeters/Product-Manager-Skills, 7.2k stars) and Idea Validator (aakashg/pm-claude-skills, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 80 20 Feature Prioritization?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,267 GitHub stars. The repository holds 716 skills in this directory. The repository was last updated on October 10, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.