req-intake SKILL.md skillA
req-intake 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-intake@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-intake/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261106.633cee9, committed Nov 6, 2026
- Size
- 4,104 bytes
- Repository stars
- 717
- License
- MIT
在需求刚提出时,先挑战它是否该做,写下一条能验证的预期效果,再用模板建飞书需求文档和飞书项目(Meegle)工作项,两边互相链接。Use when someone raises a product or technical requirement, says 提需求 / 我想要 / 能不能加, or before any requirement work starts without a doc and 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-intake) 需求跟丢,多半丢在第一步:一句话在群里提了,没有文档,没有工作项,也没人写下"做成什么样算成"。这一步我们只做三件事:问清值不值得做,写下可验证的预期效果,把文档和工作项建出来并互相挂上。提出人是这个需求的 TPM,Agent 是他的搭档,不是替他拍板。 ## 1. 先挑战,再记录 按下面顺序问提出人,答不上来的写进文档「待确认问题」,不替他编: 1. **谁在什么场景下遇到什么问题?** 要一个真实例子(会话、截图、工单、数据),没有例子就标「无实证」。 2. **不做会怎样?** 现在怎么绕过去的,绕过去的代价是什么。 3. **有没有更小的做法?** 改文档、改配置、已有功能就能解决的,直接建议不立需求。 4. **和谁有关?** 需求方、可能的执行人、要通知的人。 结论只有三种:立项 / 建议不做(附原因,提出人确认后关闭) / 先补信息。 ## 2. 写预期效果(Expected Outcome) 这是整条链路最后验收的依据(`req-outcome` 会回来对它)。每条必须同时有: | 项 | 例子 | | --- | --- | | 指标或可观察行为 | `/resume` 列表首屏加载 P95 | | 基线(现在的值,带来源) | 2.4 s,来自上周埋点 | | 目标 | ≤ 800 ms | | 怎么测、谁来测 | 同一埋点,上线后 7 天窗口,提出人看 | | 观察窗口 | 上线后 7 天 | 写不出基线就先写「基线待测」和测法,不允许只写「体验更好」「更稳定」。 ## 3. 建飞书需求文档 用 `templates/requirement-doc.md` 填好后创建(Markdown 导入): ```bash lark-cli docs +create --as user --doc-format markdown \ --title "【需求】<一句话标题>" --content @req.md \ [--parent-token <需求文件夹或 wiki 节点 token>] ``` 记下返回的文档 URL。 ## 4. 建 Meegle 工作项并互链 ```bash meegle workitem meta-create-fields --project-key <PK> --work-item-type <类型 key> --format json meegle workitem meta-roles --project-key <PK> --work-item-type <类型 key> --format json …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3cbawasynlnwcm3u/5e12d54b30a8f8c1f42ffda7fb481c70aac6eb4c7ea6d193d49eef84fe3866f2.json
Then /plugin install req-intake@markdownregistry-3cbawasynlnwcm3u 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-intake@sha256:5e12d54b30a8f8c1The 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_3cbawasynlnwcm3u)
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-intake 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-intake from somewhere else? Ask it: where did my req-intake 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-intake/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 (4104 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_3cbawasynlnwcm3u GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/req-intake GET https://markdownregistry.com/api/v1/blob/5e12d54b30a8f8c1f42ffda7fb481c70aac6eb4c7ea6d193d49eef84fe3866f2
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.