Home / alieismy / codex-three-layer-delivery · GitHub

rd-design SKILL.md skillA

rd-design from alieismy/codex-three-layer-delivery is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add alieismy/codex-three-layer-delivery/rd-design@git:20261009.a01d3df

Pins git:20261009.a01d3df in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: alieismy/codex-three-layer-delivery
Path: zh-CN/skills/rd-design/SKILL.md
Versions recorded: 5
Latest version: git:20261009.a01d3df, committed Oct 9, 2026
First version recorded: Aug 7, 2026
Size: 8,276 bytes
Repository stars: 12
License: MIT

根据已批准需求和架构决策形成可进入实现阶段的详细设计。当软件或基础设施需要规定接口契约、数据模式、关键流程、状态机、配置契约、信任边界、错误、安全、可观测性、并发或恢复行为时使用。需求、方案选择、评审、代码实现和运行执行分别路由到其责任工作流。.

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

# rd-design

基于已确认需求和技术方案产出**可进入建设阶段的详细设计**——接口定义、数据模型、关键流程、错误处理、安全设计和并发控制。

## 交付物

- 详细设计文档（接口 / 数据模型 / 流程 / 状态机）
- API 契约定义（OpenAPI / Protobuf / GraphQL Schema）
- 数据库 Schema 设计
- 安全、错误处理和可观测性设计章节
- 基础设施或集成相关任务的配置、迁移、核验和回退契约

## 执行步骤

步骤、基线读取和质量门禁仅适用于本次授权的设计范围。不适用维度应简述基于风险的理由，不得为满足清单而新增接口、数据模型或控制。

### 1. 设计输入确认

- 确认已批准需求以及重要技术方案或概要设计（`rd-solution` 产出）
- 提取已确定的：架构决策、技术栈选型、约束条件
- 识别设计范围边界：本次设计覆盖哪些模块/服务
- 确认设计项可追溯到 PRD 或已批准的设计决策
- 修订既有设计时，将每项文字改动分类为已确认的语义澄清或未解决契约；在批准证据支持更具体的责任、顺序、成功条件或恢复行为前，保留来源的抽象层级

**完成标准：** 每个范围内设计项均可追溯到已批准需求或决策；详细契约起草前，缺失的上游决策均已明确；修订工作将每项歧义映射为已批准含义或确切缺失的契约。

### 2. 接口设计

- 定义模块间接口契约（入参、出参、不变式、前置条件、后置条件、错误码、顺序和幂等性要求）
- 内部接口与外部接口分别标注
- API 版本策略说明
- 接口变更的向后兼容性约束

**完成标准：** 每个接口均有归属、输入、输出、不变式、失败行为、适用时的顺序或幂等语义，以及兼容性边界。

### 3. 数据模型设计

- 实体关系图（ER Diagram），标注主键、外键、索引
- 字段级设计：类型、长度、约束、默认值、是否可空
- 数据生命周期：创建 → 更新 → 归档 → 删除
- 数据一致性策略：强一致 / 最终一致 / 补偿

**完成标准：** 每个持久化或交换数据元素均有类型与约束语义、生命周期归属、适用时的关系或索引理由，以及明确的一致性模型。

### 4. 关键流程设计

- 核心业务流程的时序图或流程图
- 每个流程标注：正常路径、异常路径、超时处理
- 并发控制策略：锁类型、乐观/悲观、重试策略
- 幂等性设计：哪些操作必须幂等，如何保证

**完成标准：** 每个关键流程均覆盖成功、失败、超时、重试、并发和幂等行为，尤其是会改变系统状态的边界。

### 5. 状态机设计（如适用）

- 状态定义与合法转换
- 无效转换的处理策略
- 并发状态修改的冲突解决
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add alieismy/codex-three-layer-delivery/rd-design@sha256:43ef3341c161abed

The line at the top of this page pins the label git:20261009.a01d3df, 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](https://markdownregistry.com/badge/art_7cfgc3nehx3qxzn3.svg)](https://markdownregistry.com/a/art_7cfgc3nehx3qxzn3)

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

Versions

The registry has recorded 5 versions of this file, between Aug 7, 2026 and Oct 9, 2026, about one every 16 days.

version	committed	commit	size	audit
git:20261009.a01d3df latest	2026-10-09	a01d3df	8,276 B	A	view · diff
git:20260917.a51da3c	2026-09-17	a51da3c	7,872 B	A	view · diff
git:20260914.412d988	2026-09-14	412d988	7,082 B	A	view · diff
git:20260818.b6ada41	2026-08-18	b6ada41	6,968 B	A	view · diff
git:20260807.e82ae86	2026-08-07	e82ae86	6,968 B	A	view

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 (8276 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

alieismy/codex-three-layer-delivery · 12 stars · license MIT · pushed 2026-10-14 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_7cfgc3nehx3qxzn3
GET https://markdownregistry.com/api/v1/resolve?ref=alieismy/codex-three-layer-delivery/rd-design
GET https://markdownregistry.com/api/v1/blob/43ef3341c161abedf1e99563d02895d0f2d583ce88bfcb714f6d0899a3798ca0

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 alieismy/codex-three-layer-delivery

AGENTS.md AGENTS.md file

alieismy/codex-three-layer-delivery · AGENTS.md

git:20261014.84e7edc · audit A · 12 stars

rd-delivery SKILL.md skill

alieismy/codex-three-layer-delivery · skills/rd-delivery/SKILL.md · Coordinate decision or design document delivery. Use when the user explicitly requests multi-stage or multi-document…