req-ship SKILL.md skillA

req-ship from minimax-ai/mcode-stack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add minimax-ai/mcode-stack/req-ship@git:20261106.633cee9

Pins 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-ship/SKILL.md
Versions recorded
1
Latest version
git:20261106.633cee9, committed Nov 6, 2026
Size
2,820 bytes
Repository stars
717
License
MIT

上线前做就绪检查(回滚方案、可观测性、完成定义 DoD),全部有证据后再推进 Meegle 状态或节点。Use before a requirement is deployed or marked done, when someone says 可以上线了吗 / 准备发布, or before transitioning the work item to a released state.

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-ship)

「代码合了」不等于「可以上线」,更不等于「需求完成」。这一步把上线前必须有的东西逐条对证据,缺一条就不推进状态。

## 1. 就绪清单

| 项 | 要的证据 | 缺了怎么办 |
| --- | --- | --- |
| 完成定义(DoD) | design 里的检查点逐条打勾,附 PR、测试输出链接 | 回 design 或实施 |
| 回滚方案 | 具体操作(回退版本号、开关名、命令)和谁有权限执行 | 写出来再上 |
| 可观测性 | 能看到 intake 预期效果指标的看板或查询,上线前截一次基线 | 先补埋点,否则 outcome 无法验收 |
| 影响面通知 | 波及面里列的人或团队已知会(链接) | 提出人去通知 |
| 发布窗口 | 时间、负责人 | 和负责人对齐 |

证据看真实输出:CI 是在最终提交上跑的吗?测试有没有被过滤跳过?

## 2. 写回文档

把清单和证据写进「8. 上线记录」。

## 3. 推进 Meegle

先查这个工作项是状态流还是节点流、当前能去哪里、需要什么必填项:

```bash
# 状态流
meegle workflow list-state-transitions --project-key <PK> --work-item-id <ID> --format json
meegle workflow list-state-required --project-key <PK> --work-item-id <ID> --state-key <目标状态 key> --format json
meegle workflow transition-state --project-key <PK> --work-item-id <ID> --transition-id <transition_id>

# 节点流
meegle workflow get-node --project-key <PK> --work-item-id <ID> --format json
meegle workflow transition --project-key <PK> --work-item-id <ID> --node-id <节点 key> --action confirm
```

`list-state-required` 默认返回全部必填项;加 `--mode unfinished` 只看还没填的。

流转前把命令和目标状态给提出人看,确认后执行;流转后用 `workitem get` 读回状态。

注意:推进到「已上线」不是「已完成」。关闭留给 `req-outcome`。

## 输出
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xxqdnidgefeqod6z/c88fd4c2aa54013b1d9d5302cb3d74dbf4941162c0bee10d1425d61a2a4200e8.json

Then /plugin install req-ship@markdownregistry-xxqdnidgefeqod6z 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.

The exact contents, by fingerprint
mdr add minimax-ai/mcode-stack/req-ship@sha256:c88fd4c2aa54013b

The 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_xxqdnidgefeqod6z.svg)](https://markdownregistry.com/a/art_xxqdnidgefeqod6z)

7 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in minimax-ai/mcode-stack/req-ship 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-ship from somewhere else? Ask it: where did my req-ship 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)

versioncommittedcommitsizeaudit
git:20261106.633cee9 latest2026-11-06 633cee9 2,820 BA view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (2820 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

GitHub

minimax-ai/mcode-stack · 717 stars · license MIT · pushed 2026-11-11 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_xxqdnidgefeqod6z
GET https://markdownregistry.com/api/v1/resolve?ref=minimax-ai/mcode-stack/req-ship
GET https://markdownregistry.com/api/v1/blob/c88fd4c2aa54013b1d9d5302cb3d74dbf4941162c0bee10d1425d61a2a4200e8

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.

More from minimax-ai/mcode-stack

lifting-loops SKILL.md skill
minimax-ai/mcode-stack · stacks/jiachen/skills/lifting-loops/SKILL.md · Finds loops where the user keeps acting as a manual step for agents (retrying, judging output, approving, carrying…
git:20261028.e7307b0 · audit A · 717 stars
making-content SKILL.md skill
minimax-ai/mcode-stack · stacks/jiachen/skills/making-content/SKILL.md · Content production in three modes: rewrite, Xiaohongshu (小红书) image post, short video. Rewrite (default): turns an…
git:20261028.e7307b0 · audit A · 717 stars
pr-description SKILL.md skill
minimax-ai/mcode-stack · stacks/jiachen/skills/pr-description/SKILL.md · Draft or check a pull request description in a fixed format (background, changes, behavior changes, out of scope…
git:20261111.0db1b4f · audit A · 717 stars
pr-quiz SKILL.md skill
minimax-ai/mcode-stack · stacks/jiachen/skills/pr-quiz/SKILL.md · Write multiple-choice questions that check whether a PR's author understands their change. Use only when the MCode…
git:20261111.0db1b4f · audit A · 717 stars
pr-review-ci SKILL.md skill
minimax-ai/mcode-stack · stacks/jiachen/skills/pr-review-ci/SKILL.md · Connects a GitHub or GitLab repository to the MCode Review CI and keeps the setup current. Use when someone adds MCode…
git:20261111.0db1b4f · audit A · 717 stars
pr-review-tuning SKILL.md skill
minimax-ai/mcode-stack · stacks/jiachen/skills/pr-review-tuning/SKILL.md · The weekly self-tuning loop for the MCode Review bot on GitHub or GitLab. Measures the bot on a repository's recent PRs…
git:20261111.0db1b4f · audit A · 717 stars
pr-review SKILL.md skill
minimax-ai/mcode-stack · stacks/jiachen/skills/pr-review/SKILL.md · Review a pull request or the current branch with the MCode Review rules (severity, evidence ladder, lens checklists…
git:20261111.0db1b4f · audit A · 717 stars
req-design SKILL.md skill
minimax-ai/mcode-stack · stacks/req-tpm/skills/req-design/SKILL.md · 为已排期的需求做方案:列至少两个选项、写决策记录、评估波及面(blast radius)、定验收检查点,全部落进需求文档。Use when a requirement is scheduled and before…
git:20261106.633cee9 · audit A · 717 stars
req-intake SKILL.md skill
minimax-ai/mcode-stack · stacks/req-tpm/skills/req-intake/SKILL.md · 在需求刚提出时,先挑战它是否该做,写下一条能验证的预期效果,再用模板建飞书需求文档和飞书项目(Meegle)工作项,两边互相链接。Use when someone raises a product or technical…
git:20261106.633cee9 · audit A · 717 stars
req-outcome SKILL.md skill
minimax-ai/mcode-stack · stacks/req-tpm/skills/req-outcome/SKILL.md · 上线后对照 intake 写下的预期效果收集证据,判断是否达成;没达成就写清差距和下一步;只有拿到证据才关闭需求。Use after the observation window of a shipped requirement…
git:20261106.633cee9 · audit A · 717 stars
req-prioritize SKILL.md skill
minimax-ai/mcode-stack · stacks/req-tpm/skills/req-prioritize/SKILL.md · 对一个已受理的需求,对照当前在做的工作(WIP)评估成本、影响、风险,给出排期建议和理由;提出人提建议,负责人拍板。Use after req-intake, at backlog grooming or sprint planning…
git:20261106.633cee9 · audit A · 717 stars
req-track SKILL.md skill
minimax-ai/mcode-stack · stacks/req-tpm/skills/req-track/SKILL.md · 按固定节奏跟进进行中的需求,用站会格式记录进展、阻塞和下一步;超过约定时间没有更新的需求要显式标出来,不能悄悄沉下去。Use for daily or weekly requirement check-ins, when asked…
git:20261106.633cee9 · audit A · 717 stars

Every file in minimax-ai/mcode-stack

Browse by kind, by grade A, or by owner.