req-outcome SKILL.md skillA
req-outcome 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-outcome@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-outcome/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261106.633cee9, committed Nov 6, 2026
- Size
- 2,377 bytes
- Repository stars
- 717
- License
- MIT
上线后对照 intake 写下的预期效果收集证据,判断是否达成;没达成就写清差距和下一步;只有拿到证据才关闭需求。Use after the observation window of a shipped requirement, when someone asks 这个需求效果怎么样 / 可以关了吗, or before closing a work item.
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-outcome) 需求的终点是效果,不是上线。我们只在证据对上 intake 的预期效果之后关闭需求。 ## 1. 取回预期效果 ```bash lark-cli docs +fetch --as user --doc <URL> --keyword "预期效果" --context-after 3 ``` 读出每一行的指标、基线、目标、测法、观察窗口。观察窗口没到,就只记中期读数,不下结论。 ## 2. 按原测法取数 用 intake 写的同一个测法、同一个口径取数,自己复算一次。换了口径要写明,并说明为什么。不允许用「感觉好多了」「用户反馈不错」代替指标;定性反馈可以附上,但不算达成证据。 ## 3. 逐条判定 | 预期 | 基线 | 目标 | 实测(来源) | 结论 | | --- | --- | --- | --- | --- | | ... | ... | ... | ...(看板链接/查询) | 达成 / 未达成 / 无法判断 | - **未达成**:写差距、可能原因(带证据)、下一步(继续优化 / 新需求 / 接受现状),下一步要有人和时间。 - **无法判断**:通常是没埋点或口径变了,写清缺什么,回到 `req-ship` 补可观测性。 ## 4. 写回并关闭 把表格写进「9. 效果验收」。 全部达成,或提出人和负责人书面接受了未达成项,才推进到关闭状态(命令同 `req-ship` 第 3 节)。未达成且有后续时,在工作项评论里写下一步和新需求链接: ```bash meegle comment add --project-key <PK> --work-item-id <ID> --content "<验收结论 + 文档链接>" ``` ## 输出 验收表、结论、关闭与否;没关闭时写下一次验收时间。 ## 用到的命令 先确认身份和空间(每个会话一次): ```bash meegle project search --project-key "<空间名或 key>" --format json meegle workitem meta-types --project-key <PK> --format json lark-cli docs +fetch --as user --doc <需求文档 URL> --scope outline ``` 字段 key、状态 key、transition_id 一律现查,不要凭记忆填,见 `templates/meegle-field-mapping.md`。
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_obcpo6wtybmfdcjp/a4b9b4c780e7fbeb1fecea593c9a674418fdf8277d6100fccaa8094052cc77d1.json
Then /plugin install req-outcome@markdownregistry-obcpo6wtybmfdcjp 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-outcome@sha256:a4b9b4c780e7fbebThe 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_obcpo6wtybmfdcjp)
7 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-outcome 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-outcome from somewhere else? Ask it: where did my req-outcome 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-outcome/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 (2377 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_obcpo6wtybmfdcjp GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/req-outcome GET https://markdownregistry.com/api/v1/blob/a4b9b4c780e7fbeb1fecea593c9a674418fdf8277d6100fccaa8094052cc77d1
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.