prioritize
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Organize and prioritize the roadmap using releases and backlog triage. Shows kanban state, detects imbalances, recommends scoping. Also handles Kano import, audit, and roadmap export. Triggers on: "prioritize", "show roadmap", "triage", "scope to release", "review issues", "audit", "clean up", "check for duplicates".
20 other projects use a version of this.
Adopted by
Most recently taken up by
- 5hirish/ducttheir own version, first seen Nov 8, 2026
- eggs-gd/career-spacetheir own version, first seen Nov 8, 2026
- raphaeltm/simple-agent-managertheir own version, first seen Nov 7, 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 6 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
nbirknerSkillinterview-guide
Use when preparing to conduct user research interviews and needing structured JTBD-based questions. Also use when starting a new discovery research effort or when existing interview questions feel generic. Keywords: interview guide, user research questions, discovery interview, JTBD questions, research script.
Also in 3 projects that use this
launchapp-devSkilljourney-map
Create an end-to-end user journey map with stages, touchpoints, emotions, pain points, and opportunity areas. Use when mapping the full user experience for a product, feature, or service.
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
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★ 69same 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.
- addSkill
- askSkill
- buildSkill
- continueSkill
- decomposeSkill
- handoffSkill
- harlanSkill
- initSkill
- issuesSkill
- kaelSkill
- lyraSkill
- margotSkill
- miraSkill
- noteSkill
- planSkill
- prototypeSkill
- releaseSkill
- reviewSkill
- rookSkill
- sableSkill
- salSkill
- scopeSkill
- shipSkill
- testSkill
- updateSkill
- ux-walkthroughSkill
- versionSkill
- visual-promptSkill
- vossSkill
- whats-nextSkill
- wrenSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“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.
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.

