req-track SKILL.md skillA
req-track 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-track@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-track/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261106.633cee9, committed Nov 6, 2026
- Size
- 2,693 bytes
- Repository stars
- 717
- License
- MIT
按固定节奏跟进进行中的需求,用站会格式记录进展、阻塞和下一步;超过约定时间没有更新的需求要显式标出来,不能悄悄沉下去。Use for daily or weekly requirement check-ins, when asked 这个需求到哪了 / 有没有卡住的, or from a scheduled routine.
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-track) 需求不是做砸的,多数是没人问着慢慢沉掉的。这一步就是定期问一句,并且把「没人更新」本身当成一条要上报的信息。 ## 1. 约定节奏 在 intake 或 design 时和提出人约好:开发中默认每个工作日一次,排队中每周一次。写进文档「1. 文档信息」的「跟进节奏」。 ## 2. 拉状态 ```bash meegle workitem get --project-key <PK> --work-item-id <ID> --format json meegle workitem list-op-records --project-key <PK> --work-item-id <ID> --format json meegle comment list --project-key <PK> --work-item-id <ID> --format json ``` 多个需求时用 `workitem query` 按提出人或标签筛,见 meegle skill 的 `mql-people-roles.md`。 ## 3. 站会三问 对每个需求只写三行,事实来自上面的记录和关联的 PR/CI,不来自猜测: ```text 进展:自上次以来完成了什么(附链接) 阻塞:卡在哪、等谁、从哪天开始 下一步:谁、做什么、预计何时 ``` ## 4. 判定停滞 满足任一条就标 **停滞**: - 操作记录和评论在约定节奏的两倍时间内没有新内容; - 同一阻塞连续两次跟进没变化; - 计划时间已过但状态没动。 停滞不自动改状态、不自动催人。我们做的是:在给提出人的报告里置顶这一项,写清停了多久、最后一次动静是什么、建议找谁。提出人决定是否在工作项上评论或 @ 人: ```bash meegle comment add --project-key <PK> --work-item-id <ID> --content "<站会三行>" ``` ## 5. 记录 把每次的三行追加到文档「7. 进展记录」末尾,保持时间顺序: ```bash lark-cli docs +update --as user --doc <URL> --command append --doc-format markdown --content @standup.md ``` ## 输出 一张表:需求、状态、进展、阻塞、下一步、是否停滞。停滞项放最上面。只读汇总,不给人排名。 ## 用到的命令 先确认身份和空间(每个会话一次): ```bash meegle project search --project-key "<空间名或 key>" --format json …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_e6dc2zbe2k2tze5c/49de31f5725c8c1bbbfded1b8dd110944a67d3bf5ae20a1134b87867b969f884.json
Then /plugin install req-track@markdownregistry-e6dc2zbe2k2tze5c 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-track@sha256:49de31f5725c8c1bThe 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_e6dc2zbe2k2tze5c)
3 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-track 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-track from somewhere else? Ask it: where did my req-track 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-track/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 (2693 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_e6dc2zbe2k2tze5c GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/req-track GET https://markdownregistry.com/api/v1/blob/49de31f5725c8c1bbbfded1b8dd110944a67d3bf5ae20a1134b87867b969f884
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.