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.
A skill your agent uses when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano.
Install Pm Prioritize
$ npx skills add serejaris/personal-corp-os --skill pm-prioritize -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install serejaris/personal-corp-os pm-prioritize --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pm-prioritize .claude/skills/pm-prioritize && rm -rf skills-srcUse ~/.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/
Install the "pm-prioritize" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prioritize into .claude/skills/pm-prioritize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prioritize", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prioritizeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add serejaris/personal-corp-os --skill pm-prioritize -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install serejaris/personal-corp-os pm-prioritize --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pm-prioritize .agents/skills/pm-prioritize && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pm-prioritize" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prioritize into .agents/skills/pm-prioritize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prioritize", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add serejaris/personal-corp-os --skill pm-prioritize -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install serejaris/personal-corp-os pm-prioritize --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pm-prioritize .cursor/skills/pm-prioritize && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pm-prioritize" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prioritize into .cursor/skills/pm-prioritize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prioritize", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/serejaris/personal-corp-os.git --path skills/pm-prioritize--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add serejaris/personal-corp-os --skill pm-prioritize -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install serejaris/personal-corp-os pm-prioritize --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pm-prioritize .gemini/skills/pm-prioritize && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pm-prioritize" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prioritize into .gemini/skills/pm-prioritize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prioritize", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install serejaris/personal-corp-os pm-prioritizeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add serejaris/personal-corp-os --skill pm-prioritize -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pm-prioritize .github/skills/pm-prioritize && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pm-prioritize" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prioritize into .github/skills/pm-prioritize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prioritize", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add serejaris/personal-corp-os --skill pm-prioritize -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install serejaris/personal-corp-os pm-prioritize --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/serejaris/personal-corp-os.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pm-prioritize .opencode/skills/pm-prioritize && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pm-prioritize" agent skill from https://github.com/serejaris/personal-corp-os/tree/main/skills/pm-prioritize into .opencode/skills/pm-prioritize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pm-prioritize", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pm-prioritize- GitHub stars
- 229
- Token cost
- ~2.3k tokens
- SKILL.md length
- 997 words
- Files
- 4 (incl. assets)
- Skills in repo
- 36
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano.
- Works in 4 steps: Pick a framework → Score requirements → Output ranking → …
- Ranking a list of requirements
- SKILL.md covers Inputs, Optional config, Research commands… and Step 1 — Pick a framework, plus 7 more sections
- Calls gh
What it does
Pm Prioritize is an agent skill from serejaris/personal-corp-os. Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do NOT auto-trigger. Triggers on "/pm-prioritize", "/prioritize", "приоритизация", "ранжируй бэклог", "RICE-анализ", "prioritize requirements", "RICE", "ICE", "MoSCoW", "Kano", "rank backlog".
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including assets (for example `README.md` and `README.ru.md`).
It sits in Product & Project Management, covering Prioritization frameworks. The repository describes itself as: Personal Corp OS — управление личной компанией через AI-агентов: задачи вне головы, отделы вместо памяти, недельное ретро. Открытые скиллы для Claude Code и Codex. The licence is MIT.
When your agent uses it
- Ranking a list of requirements
- Backlog items using RICE / ICE / MoSCoW / Kano
- Ранжируй бэклог
- Prioritize requirements
Example prompts
- “/pm-prioritize”
- “/prioritize”
- “RICE-анализ”
- “/pm-prioritize”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 95e36c3. 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
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
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
Pm Prioritize loads about 2.3k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 997 words of instructions outside code blocks.
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 serejaris/personal-corp-os at commit 95e36c3, republished under its MIT licence (© serejaris). 997 words, ~2,328 tokens.
Download SKILL.mdSave it as
.claude/skills/pm-prioritize/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- pm-prioritize
- description
- Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Built-in decision tree picks the right framework based on data availability and decision context. Output is a transparent matrix, 2×2 Impact/Effort quadrant, and a Sprint allocation proposal. User-invoked only — do NOT auto-trigger. Triggers on "/pm-prioritize", "/prioritize", "приоритизация", "ранжируй бэклог", "RICE-анализ", "prioritize requirements", "RICE", "ICE", "MoSCoW", "Kano", "rank backlog".
pm-prioritize — Rank requirements with RICE / ICE / MoSCoW / Kano
Part of the Personal Corp framework — running a one-person business through AI agents.
Rank a list of requirements using a structured framework. A built-in decision tree picks the right framework based on data availability and decision context. Output is transparent and traceable, so a team can argue with the scores instead of the recommendation.
Inputs
| Field | Required | Notes |
|---|---|---|
| Requirement list | yes | Name + brief description; ≥ 3 items. Can take a pain-point list from /pm-feedback or a feature list from /pm-prd |
| Framework | no | RICE / ICE / MoSCoW / Kano; auto-recommended if not given |
| Business goal | no | Current focus (growth / retention / revenue / efficiency); affects weighting |
| Resource constraint | no | Available dev capacity (person-days or Story Points) |
Optional config
Most of the skill works out-of-box. If you want stable defaults across runs, add an ## Prioritize Config section to your project's CLAUDE.md:
## Prioritize Config
### Default framework (optional)
If unset, the skill auto-recommends per the decision table below.
- default_framework: RICE | ICE | MoSCoW | Kano
### Default resource constraint (optional)
Used in the Sprint allocation step. Skip if you'd rather state it per run.
- sprint_capacity: 20 person-days per Sprint
### Backlog source (optional)
Where the skill should fetch the requirement list from when you don't paste one.
- backlog_source: gh-issues # gh-issues | github-project | tasks-file | paste
- gh_owner: your-github-handle
- gh_repo: your-main-repo
- gh_label: backlog
- tasks_file: docs/backlog.mdWhen a config field is set, the skill uses it silently. When unset, the skill asks (see "When input is incomplete").
Research commands (auto-discovery)
If the user points at a backlog source instead of pasting items, the skill can pull the list itself:
# GitHub issues by label
gh issue list -R $OWNER/$REPO --label $LABEL --state open \
--json number,title,body --limit 100
# GitHub Project items
gh project item-list $PROJECT_ID --owner $OWNER --format json
# Local backlog file
cat $TASKS_FILEStep 1 — Pick a framework
If unspecified, recommend per this decision table:
| Condition | Recommended | Why |
|---|---|---|
| Have user-impact data per item (DAU, conversion), trustworthy | RICE | Most quantitative, traceable |
| Have intuition but no precise data | ICE | Quick scoring, tolerates subjectivity |
| Need 4-bucket alignment fast (e.g. team meeting) | MoSCoW | Forces "must" / "won't" consensus |
| Need to understand requirement nature, plan features | Kano | Identifies delight features |
Framework comparison:
| Framework | Use case | Strength | Limit | Time |
|---|---|---|---|---|
| RICE | Data-supported quarterly planning | Most objective, comparable | Depends on data quality | Medium |
| ICE | Fast decisions, brainstorming | Simple, fast | Highly subjective | Low |
| MoSCoW | Release planning, stakeholder alignment | Forces consensus | Easy to put everything in Must | Low |
| Kano | Feature planning, satisfaction research | Identifies delighters | Needs user research data | High |
Step 2 — Score requirements
RICE (default)
| Dimension | Meaning | Scoring | Common error |
|---|---|---|---|
| Reach | Users impacted in one cycle | Concrete number ("5000 users/month") | "All users theoretically" as Reach |
| Impact | Per-user impact magnitude | 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal | Everything gets 3 |
| Confidence | Confidence in the estimate | 100% = data, 80% = indirect evidence, 50% = gut | 100% with no data |
| Effort | Total person-months across all roles | Includes design + dev + QA + integration | Counting only dev |
RICE Score = (R × I × C) / E — higher = higher priority.
Calibration mechanism:
- Score the same dimension across all items first (all R, then all I) — avoids per-item anchoring bias
- R calibration: pick a baseline ("login: affects 100% of users"), score others relative
- I calibration: ≤ 50% of items can score 3 — forces differentiation
- E calibration: must include design (20%) + dev (50%) + QA (20%) + integration (10%)
ICE (fast)
Score 1-10 on each dimension. ICE Score = I × C × E / 10.
| Dimension | Scoring |
|---|---|
| Impact | 1 = trivial, 5 = medium, 10 = transformational |
| Confidence | 1 = pure guess, 5 = indirect evidence, 10 = A/B test data |
| Ease | 1 = very hard (> 3 months), 5 = medium (2-4 weeks), 10 = trivial (< 1 day) |
MoSCoW
| Bucket | Definition | Suggested share |
|---|---|---|
| Must Have | Without it, can't ship; users can't use core feature | ≤ 60% |
| Should Have | Important but has workaround; one-Sprint delay non-fatal | ~ 20% |
| Could Have | Nice-to-have; better with, fine without | ~ 10% |
| Won't Have (this time) | Explicitly out of scope; possibly later | ~ 10% |
Common trap: everything ends up Must Have. Counter: cap Must Have at 60%, force trade-offs.
Kano
| Type | Trait | Detection | Strategy |
|---|---|---|---|
| Must-be | Absence → dissatisfaction; presence → taken for granted | Users don't ask for it but rage when missing | Reach passing grade, don't over-invest |
| One-dimensional | More = more satisfaction (linear) | Users actively request | Core competitive area, top-tier execution |
| Attractive | Absence → no dissatisfaction; presence → delight | Unexpected, evokes "wow" | Differentiator (decays to one-dimensional over years) |
| Indifferent | Doesn't matter either way | No user reaction | Don't invest |
| Reverse | Presence reduces satisfaction | Adds complexity, annoys users | Remove immediately |
Kano decay: today's Attractive feature becomes One-dimensional, then Must-be over 2-3 years (e.g. fingerprint unlock). Continuously create new delighters.
Show full SKILL.md (359 more words)Show less
Step 3 — Output ranking
RICE results table:
| Rank | Requirement | R | I | C | E | RICE Score | Recommendation |
|---|---|---|---|---|---|---|---|
| 1 | {name} | {n} | {0.25-3} | {50-100%} | {pm} | {score} | This cycle |
Impact × Effort 2×2:
| Quadrant | Impact | Effort | Strategy | Items |
|---|---|---|---|---|
| Quick Wins | High | Low | Do first | {list} |
| Strategic | High | High | Plan carefully | {list} |
| Fill-ins | Low | Low | When idle | {list} |
| Avoid | Low | High | Don't do | {list} |
Sprint allocation:
- Allocate per
sprint_capacity(config) or stated resource constraint - Quick Wins fill first; Strategic by RICE Score
- Reserve 10-20% per Sprint for unexpected work
Step 4 — Decision log
- Core trade-offs: why A over B this cycle
- Disputed items: which ranks may be contested, and why
- Confidence flags: which scores have C < 80% — propose validation experiments
- Next-cycle candidates: Won't-Have items most likely to promote next cycle
Quality bar
- Every score has a one-sentence rationale
- Effort includes design + dev + QA + integration
- C < 80% items get "validate via small experiment" tag
- Must Have ≤ 60% of total
- Calibration mechanism applied to avoid anchoring
Red lines
- Not a decision-maker — output is a recommendation; the final call is the team's
- No hidden assumptions — every score's assumption is explicit
- Never ignore Effort — no "must do" recommendation based on Impact alone
When input is incomplete
- No backlog source provided → ask: "Where is the list — paste, file path, or a GitHub issues filter (owner/repo + label or milestone)?"
- No business goal → ask: "Current focus this cycle — growth / retention / revenue / efficiency? Optional, but it tightens the recommendation."
- No resource constraint → ask: "Available capacity for the next cycle — person-days or Story Points? Optional, but needed for Sprint allocation."
- Framework unset → don't ask. Auto-recommend per the Step 1 decision table and propose it with a one-sentence rationale; user confirms or overrides.
- < 3 requirements → still rank, but flag "sample too small, add more for stability"
- No data at all → switch to ICE or MoSCoW; tag "qualitative ranking due to missing quantitative data"
Related skills
weekly-planning— uses the ranked backlog from this skill to pick weekly OKRs / outcomes. Prioritization feeds OKR selection, not replaces it.weekly-retro— feeds the next backlog with retro findings and carry-over items/pm-user-stories— top-priority requirements → break into Stories/pm-prd— Must-Have requirements → write PRDs
© serejaris, MIT. 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 3 other files (assets) in skills/pm-prioritize of serejaris/personal-corp-os.
- SKILL.md
- README.md
- README.ru.md
- assets/illustration.png
Open the folder on GitHubat commit 95e36c3
Compare with similar skills
Pm Prioritize 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pm Prioritize this skillserejaris/personal-corp-os | 229 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Prioritization Framework Advisordeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~4.2k | Automated safety check: Pass | Custom licence | |
| Strategic Roadmap Planningdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~4.7k | Automated safety check: Pass | Custom licence | |
| Idea Validatoraakashg/pm-claude-skills | 112 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Triagejoa23/linear-cli | 144 | — | ~699 | Automated safety check: Pass | MIT |
Similar skills
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.
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
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.
Triage
joa23/linear-cli
Triage and prioritize Linear backlog issues using the linear CLI.
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.
More from serejaris/personal-corp-os
All 36 skills in this repoWeekly Planning
serejaris/personal-corp-os
A skill your agent uses when the user is transitioning from a completed retro into a weekly plan, choosing weekly outcomes, scheduling a full ISO week, or asking for "план на неделю", "weekly…
Gh Issues
serejaris/personal-corp-os
A skill your agent uses when creating, searching, updating, or managing GitHub issues via CLI.
Product Data Audit
serejaris/personal-corp-os
A skill your agent uses when auditing a product, business, or project ecosystem — analyzing data sources, decision loops, bottlenecks, and implementation contours.
Tg Bot Ops
serejaris/personal-corp-os
A skill your agent uses when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway.
Audit Agent Rules
serejaris/personal-corp-os
Audits the agent rules in the current folder (AGENTS.md, nested AGENTS.md files) and the skill descriptions the agent sees at start, then reports what to cut, move or rewrite and edits only after…
Make Landing
serejaris/personal-corp-os
Создаёт несколько вариантов дизайна 2D-поверхности (лендинг, герой, обложка, слайды): свой визуальный референс и автор на вариант, полный design.md с UTC/SHA-256 до кода, проверка в браузере…
Related
Categories
Questions about Pm Prioritize
What does Pm Prioritize do?
A skill your agent uses when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano. Pm Prioritize is an agent skill from serejaris/personal-corp-os. Use when ranking a list of requirements, features, or backlog items using RICE / ICE / MoSCoW / Kano.
When should I use Pm Prioritize?
Pm Prioritize fits situations like: ranking a list of requirements; backlog items using RICE / ICE / MoSCoW / Kano; Ранжируй бэклог; prioritize requirements.
How do I install Pm Prioritize in Claude Code?
Run `npx skills add serejaris/personal-corp-os --skill pm-prioritize -a claude-code`. Or copy the skill folder (skills/pm-prioritize in serejaris/personal-corp-os) into .claude/skills/pm-prioritize in your project. Claude Code loads it when a task matches its description.
How do I install Pm Prioritize in Codex?
Run `npx skills add serejaris/personal-corp-os --skill pm-prioritize -a codex`. Or copy the skill folder (skills/pm-prioritize in serejaris/personal-corp-os) into .agents/skills/pm-prioritize in your project. Codex loads it when a task matches its description.
Can I use Pm Prioritize 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 serejaris/personal-corp-os --skill pm-prioritize -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pm-prioritize, .gemini/skills/pm-prioritize, .github/skills/pm-prioritize and .opencode/skills/pm-prioritize in your project.
What does Pm Prioritize need to run?
Going by SKILL.md and its folder, Pm Prioritize needs the command-line tools its instructions call (gh).
Does Pm Prioritize access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Pm Prioritize 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 Pm Prioritize use?
Pm Prioritize is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pm Prioritize use?
About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pm Prioritize?
Skills that share tags, products or a category with Pm Prioritize: 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 Pm Prioritize?
serejaris (a GitHub user) maintains it in serejaris/personal-corp-os, which has 229 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 7, 2026.
Source: serejaris/personal-corp-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.