req-design SKILL.md skillA
req-design 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-design@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-design/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261106.633cee9, committed Nov 6, 2026
- Size
- 3,145 bytes
- Repository stars
- 717
- License
- MIT
为已排期的需求做方案:列至少两个选项、写决策记录、评估波及面(blast radius)、定验收检查点,全部落进需求文档。Use when a requirement is scheduled and before implementation, 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-design)
方案讨论最容易散在群聊和会议里。我们要求结论回到需求文档,形成一条能被后来人读懂的决策记录。
## 1. 输入
- 需求文档(`lark-cli docs +fetch --as user --doc <URL>`),重点读背景、预期效果、待确认问题。
- 相关代码或系统现状:从真实仓库和文档里读,不凭印象。
待确认问题里还有影响方案的项,先回去问提出人,不进入设计。
## 2. 至少两个选项
每个选项一段:做法、改动范围、成本、主要风险、放弃它的理由。「什么都不改,只改文档/流程」也算一个选项,值得写。
## 3. 决策记录
```text
决定:选项 B
原因:...
放弃了:选项 A,因为 ...
谁定的、何时:...
假设(被推翻时要重新评审):...
```
## 4. 波及面
列出这次改动可能波及、但不在 diff 里的地方:调用方、配置、数据迁移、对外接口、文档、其他团队。每条写「怎么确认没坏」(一个测试、一条命令、一个负责人确认)。
## 5. 验收检查点
把 intake 的预期效果拆成实施过程中的检查点,每个检查点有可执行的检查方式:
| 检查点 | 何时 | 怎么查 | 通过标准 |
| --- | --- | --- | --- |
| 方案评审通过 | 开发前 | 文档评审记录 | 负责人确认 |
| 关键路径测试 | 合入前 | `<测试命令>` | 全绿,且新测试在旧代码上失败 |
| 灰度指标 | 上线后 1 天 | 埋点看板 | 不劣于基线 |
## 6. 写回文档并推进节点
写进「5. 方案设计」「6. 验收检查点」(用 `+fetch --detail with-ids` 拿 block_id,再 `+update --command block_insert_after` 或 `block_replace`)。
方案评审在 Meegle 上若是一个节点,评审结论按 meegle skill 的 `sop-transition-node.md` 写:
```bash
meegle workflow get-node --project-key <PK> --work-item-id <ID> --node-id-list '["<评审节点 key>"]' --format json
meegle workflow update-node --project-key <PK> --work-item-id <ID> --node-id <评审节点 key> \
--fields '[{"field_key":"node_finished_opinion","field_value":"<评审意见>"}]'
```
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_57syacigjmdhpjhp/b5be2515d228b2b83ca751a8a650fda44cf02a5e9960b511b0733ed045af8010.json
Then /plugin install req-design@markdownregistry-57syacigjmdhpjhp 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-design@sha256:b5be2515d228b2b8The 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_57syacigjmdhpjhp)
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-design 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-design from somewhere else? Ask it: where did my req-design 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-design/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 (3145 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_57syacigjmdhpjhp GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/req-design GET https://markdownregistry.com/api/v1/blob/b5be2515d228b2b83ca751a8a650fda44cf02a5e9960b511b0733ed045af8010
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.