agentleFS
link7373link7373/agentic-pmo/.claude/skills/prioritize/SKILL.md

prioritize

Skill1 starsChanged 3 months agoMITView on GitHub

Score and rank features, ideas, or backlog items against goals using the right framework (RICE, WSJF, Kano, value/effort, MoSCoW, or weighted scoring). Use when deciding what to build next or sequencing work. Dispatches the product-manager.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-doc, weekly-plan and 9 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.
  • MehdibargachSkill

    decision-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-dytkoSkill

    weekly-plan

    Plan weekly P-Tasks with in-repo task triage and overplanning challenge

    Also in 3 projects that use this

  • nbirknerSkill

    interview-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-devSkill

    journey-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

  • arezousSkill

    status-update

    Write a status update for a project or initiative. Matches the style to the audience.

    Also in 3 projects that use this

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 4 projects that use this

The file

Files
SKILL.md

/prioritize — Rank work against goals

When to use

Choosing what to build next, sequencing initiatives, or scoping a release among competing items.

Dispatches

product-manager (lead). Pull effort estimates from product-owner/team; impact evidence from product-analyst/discovery-researcher.

Inputs

Candidate items (from roadmap, backlog, stakeholders), knowledge/product-context.md (goals/OKRs).

Steps

  1. Confirm the goal/OKR the ranking serves; drop items that don't ladder up to it.
  2. Pick the framework that fits the decision:
    • many features, one goal → RICE; sequencing a flow with timing → WSJF;
    • satisfaction strategy / feature mix → Kano; quick triage → value/effort 2×2;
    • release scope with stakeholders → MoSCoW; multi-criteria → weighted scoring.
  3. Score each item; record estimates, confidence, and assumptions. Weigh the underlying bases — value, cost/effort, risk, dependencies, time-sensitivity, and any regulatory/policy constraints that can override pure scoring.
  4. Produce a ranked, defensible order with the rationale.

Methods

knowledge/methods/prioritization-frameworks.md.

Output

A ranked list with scores and rationale; reflect ordering into knowledge/roadmap.md or knowledge/backlog.md as relevant; log the prioritization decision to knowledge/decision-log.md. Follow standards/document-standards.md.


Created by Colin Beck<br> LinkedIn: https://www.linkedin.com/in/beckcolin/<br> GitHub: https://github.com/link7373

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.