req-prioritize SKILL.md skillA
req-prioritize from minimax-ai/mcode-stack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add minimax-ai/mcode-stack/req-prioritize@git:20261106.633cee9Pins git:20261106.633cee9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- minimax-ai/mcode-stack
- Path
stacks/req-tpm/skills/req-prioritize/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261106.633cee9, committed Nov 6, 2026
- Size
- 3,395 bytes
- Repository stars
- 717
- License
- MIT
对一个已受理的需求,对照当前在做的工作(WIP)评估成本、影响、风险,给出排期建议和理由;提出人提建议,负责人拍板。Use after req-intake, at backlog grooming or sprint planning, or when someone asks 这个需求优先级多高 / 能不能插队.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 需求排优先级(req-prioritize) 优先级不是提出人喊出来的,也不是 Agent 算出来的。我们的分工是:提出人和他的 Agent 把账算清楚、给出建议,负责人(空间里配置的 PM/Owner 角色)做决定。Agent 不改别人需求的优先级。 ## 1. 拉当前 WIP ```bash meegle workitem query --project-key <PK> \ --mql "SELECT name, priority, status, current_status_operator FROM <类型 key> WHERE <状态不在已完成/已关闭>" \ --format json ``` MQL 写法先读 meegle skill 的 `references/mql-basics.md` 与 `mql-operators.md`;状态条件的具体写法见 `mql-time-status.md`。单次最多 50 条,多了按 `--session-id` 翻页。 ## 2. 三项各给一个档位和证据 | 维度 | 档位 | 必须附的证据 | | --- | --- | --- | | 影响 | 高 / 中 / 低 | 受影响人数或场景频率,来自 intake 的实证 | | 成本 | S(≤2 人日)/ M(≤1 周)/ L(>1 周) | 粗拆的步骤,谁估的 | | 风险 | 高 / 中 / 低 | 碰到的模块、数据、权限、对外接口 | 没证据的格子写「未知」,不要往中间档凑。 ## 3. 和 WIP 比 - 这个需求要占谁的时间?那个人手上已有几项在做? - 插进来会推迟哪一项?把被推迟项的名字写出来。 - 不插队的话最早什么时候能开始? ## 4. 写建议 ```text 建议:本迭代 / 下迭代 / 进 backlog / 不做 理由:(一到三条,对应上面的证据) 代价:插进来会推迟 <工作项名> 需要负责人决定的点:... ``` 把建议写进需求文档「4. 优先级评估」: ```bash lark-cli docs +fetch --as user --doc <URL> --scope outline --detail with-ids lark-cli docs +update --as user --doc <URL> --command block_insert_after \ --block-id <「4. 优先级评估」标题的 block_id> --doc-format markdown --content @prio.md ``` 在工作项上留评论并 @ 负责人(这是对外可见的动作,先给提出人看过再发): ```bash …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_s2scg2vu24qscovd/8df121fa6070e6561000798d1e7ac2a663e20e74e0e1b8b8f5c371c616bd2ddb.json
Then /plugin install req-prioritize@markdownregistry-s2scg2vu24qscovd in Claude Code. It installs git:20261106.633cee9, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add minimax-ai/mcode-stack/req-prioritize@sha256:8df121fa6070e656The line at the top of this page pins the label git:20261106.633cee9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_s2scg2vu24qscovd)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in minimax-ai/mcode-stack/req-prioritize since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of req-prioritize from somewhere else? Ask it: where did my req-prioritize come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 6, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/req-prioritize/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3395 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
minimax-ai/mcode-stack · 717 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_s2scg2vu24qscovd GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/req-prioritize GET https://markdownregistry.com/api/v1/blob/8df121fa6070e6561000798d1e7ac2a663e20e74e0e1b8b8f5c371c616bd2ddb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.