agentleFS
Sign inStart free
joinwell52-AIjoinwell52-AI/CodeFlowMu-open/skills/pm-priority-triage/SKILL.md

pm-priority-triage

Skill2 starsChanged 4 months agoMITView on GitHub

Classify CodeFlowMu tasks, risks, blocked reports, and EVAL findings as P0/P1/P2. Use when PM must decide order, owner, urgency, or whether work should be handled now, later, or held for ADMIN.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when multiple tasks or risks compete, or when ADMIN asks what should happen next.

    line 10
  2. Very specific:

    Use the structure in docs/skills/pm-playbook/priority-triage.md.

    line 21
  3. Distinctive:

    Do not treat PM priority advice as ADMIN decision.

    line 25
  4. Distinctive:

    Do not let EVAL promote itself.

    line 26
  5. Distinctive:

    Do not submit public GitHub issues automatically.

    line 27
  6. Distinctive:

    Do not bypass ADMIN.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PM Priority Triage

When to use

Use this skill when multiple tasks or risks compete, or when ADMIN asks what should happen next.

Rules

  • P0 blocks main flow or risks governance/data damage.
  • P1 affects quality or maintainability without blocking main flow.
  • P2 is optimization, documentation, or later enhancement.
  • State owner and suggested action.

Required output

Use the structure in docs/skills/pm-playbook/priority-triage.md.

Forbidden actions

  • Do not treat PM priority advice as ADMIN decision.
  • Do not let EVAL promote itself.
  • Do not submit public GitHub issues automatically.
  • Do not bypass ADMIN.

Minimal example

Issue: missing REPORT evidence
Priority: P1
Owner: DEV
Action: request fixed report with evidence

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.

Check your setup, free