prioritize

Rank root-cause initiatives by ICE with a three-item cut line.

14|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hungv47/meta-skills --skill prioritize-hungv47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prioritize
Source: https://github.com/hungv47/meta-skills/tree/main/skills/research/prioritize
Command: npx skills add https://github.com/hungv47/meta-skills --skill prioritize-hungv47

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prioritize translates a diagnosed root cause into a focused, ranked set of actionable initiatives, preventing generic growth plays and decision drift.

Core Features & Use Cases

  • Anchors initiatives to the diagnosed root cause and enforces the anti-generic test
  • Generates 5-10 concrete initiatives with explicit mechanics, targets, and effort sizing
  • Applies forced ranking before ICE scoring to set a defensible cut line (≤3 Proceed items)
  • Outputs a gate-ready artifact with owner, baseline, and kill criteria for plan-funnel handoff
  • Integrates with churn-root-cause workflows to surface domain-specific archetypes

Quick Start

Provide the root-cause anchored initiatives and the cut-line-ready ranking for execution

Frequently Asked Questions about prioritize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rank strategic initiatives using ICE scoring to enforce a cut line?

To rank initiatives using ICE, generate 5-10 concrete options anchored to a root cause, apply forced ranking, and enforce a cut line of at most three Proceed items with owners, baselines, and kill criteria.

What is the best way to translate a root cause into actionable initiatives?

Translating a root cause into initiatives requires specifying concrete mechanics, numeric target metrics with baselines, and effort sizing (S/M/L) for each option before applying forced ranking and prioritization.

How do I prevent decision drift and generic growth plays when prioritizing execution?

Preventing decision drift involves anchoring initiatives directly to a diagnosed root cause and applying an anti-generic test before ICE scoring to ensure focused, high-impact execution decisions.

Can I use this prioritization framework for churn root-cause workflows?

Yes, prioritization integrates with churn root-cause workflows by surfacing domain-specific archetypes and producing a gate-ready artifact with out-of-scope kills structured for plan-funnel handoff.

What are the limitations of forced ranking for initiative prioritization?

Forced ranking limits execution to a maximum of three Proceed items, requiring clear kill criteria and structured out-of-scope outputs, which restricts scope but prevents decision drift during execution.