prioritize
Skill2 starsChanged 49 days agoMITView on GitHub
Score and rank Ideas/ with RICE grounded in the graph. Use when the user runs /prioritize, asks which idea to build first, or wants a scored roadmap input.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- raphaeltm/simple-agent-managertheir own version, first seen Nov 15, 2026
- 5hirish/ducttheir own version, first seen Nov 8, 2026
- eggs-gd/career-spacetheir own version, first seen Nov 8, 2026
- zanellig/skillstheir own version, first seen Oct 29, 2026
- mohitkhandelwal242/ai-pm-operatortheir own version, first seen Oct 20, 2026
- Tngc93/product-management-skillstheir own version, first seen Oct 20, 2026
Used with
Projects with it also use decision-doc, weekly-plan and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MehdibargachSkilldecision-doc
Structure a product decision with options, trade-offs, and a clear recommendation. Takes a decision to make and outputs a concise decision document ready for stakeholder review.
Also in 3 projects that use this
aleksander-dytkoSkillweekly-plan
Plan weekly P-Tasks with in-repo task triage and overplanning challenge
Also in 3 projects that use this
arezousSkillstatus-update
Write a status update for a project or initiative. Matches the style to the audience.
Also in 3 projects that use this
RhyGSkillwrite-prd
Also in 3 projects that use this
SentrySkillonboard
Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.
Also in 3 projects that use this
BlockSkillplan
Draft a TDD, PRD, or lightweight plan in the conversation without committing it.
Also in 3 projects that use this
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- gitkraken/vscode-gitlens★ 10ksame name
- suboss87/FDEOps★ 940same name
- menkesu/awesome-pm-skills★ 441same name
- andreaskelm/pm-brain★ 235same name
- kv0906/pm-kit★ 138same name
- Mehdibargach/claude-code-pm-skills★ 97same name
- raphaeltm/simple-agent-manager★ 73same name
- arezous/pm-pilot★ 20same name
- 5hirish/duct★ 8same name
- eggs-gd/career-space★ 4same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- affinitySkill
- ai-personaSkill
- analytics-syncSkill
- backlogSkill
- catalogSkill
- cold-startSkill
- contradictionsSkill
- demo-dataSkill
- dovetail-syncSkill
- exportSkill
- extract-findingsSkill
- feature-panelSkill
- forget-participantSkill
- graph-lintSkill
- interview-guideSkill
- journey-mapSkill
- opportunity-treeSkill
- persona-avatarSkill
- persona-querySkill
- persona-talkSkill
- persona-voiceSkill
- persona-workshopSkill
- prdSkill
- researcherSkill
- retentionSkill
- source-syncSkill
- subject-accessSkill
- welcomeSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Read every idea in scope + its linked Evidence/Signals (+ the persona sections that reference it).
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
prioritize — Grounded RICE over Ideas/
Standard RICE with one twist that this repo makes possible: the numbers have to say where they came from. Reach cites Evidence, Confidence is derived from claim Levels (not gut-picked), and anything unknowable from research is marked TBD instead of invented.
Trigger
/prioritize ← score every file in Ideas/ (Hypotheses/ are NEVER scored — no grounding, no RICE; promote to an Idea first)
/prioritize Ideas/<file> ← score/rescore one ideaScoring rules (per idea)
- Reach — who/how many, cited from a linked
Evidence/file ("22.2% of subscribers share accounts [Shared accounts]"). No Evidence with a number →estimate, no dataand a note that/researcheror/analytics-synccould firm it up. Never invent a percentage. - Impact (0.25–3) — how directly it addresses the linked Pain; one line of reasoning tied to the Signal.
- Confidence — derived, never hand-picked, from the strongest claim Level among the idea's linked sources (canonical scale:
ai-persona/references/levels.md):- L4–L5 → High (1.0) · L3 → Medium (0.8) · L2 → Low (0.5) · L1/none → Very low (0.2)
- Stale sources (3-month rule) knock Confidence down one band — say so in the row.
- Effort — the one input research can't provide. Ask the user/team for sizing; until given,
TBD(and the RICE score staysTBD— an unranked idea is honest, a fake-ranked one isn't). - Metric to watch — the product metric this idea should move, phrased so
/analytics-synccould actually query it.
Workflow
- Read every idea in scope + its linked Evidence/Signals (+ the persona sections that reference it).
- Compute the scoring block per idea; show the full table sorted by RICE (TBD-effort rows listed separately, not silently ranked last).
- On approval, write/update each idea's
## PM scoringsection (theIdeas/_template.mdblock) — the file is the source of truth, the table is a view. - Flag ideas whose Confidence is Very low/Low as research-first, not build-first — route to
/interview-guide(that's the cheaper way to raise Confidence than shipping blind). - Offer follow-ups:
/feature-panelfor a who-benefits view of the top idea,/export ticketfor the winner,/opportunity-treefor the strategic view.
Rules
- Confidence derivation is mechanical — if the user wants to override it, record the override explicitly ("Confidence raised by PM judgment, data says L3") rather than silently editing.
- Rescoring after new research is expected and cheap — new Signals/Evidence change Levels, Levels change Confidence; say what moved and why.
- This skill edits only
Ideas/scoring blocks — never the underlying Evidence/Signals.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

