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

rd-solution SKILL.md skillA

rd-solution 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-solution@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-solution/SKILL.md
Versions recorded: 5
Latest version: git:20261009.a01d3df, committed Oct 9, 2026
First version recorded: Jul 31, 2026
Size: 7,978 bytes
Repository stars: 12
License: MIT

把已批准需求或可研输入转化为技术方案、概要设计、解决方案架构或建设方案。当软件、基础设施、网络或 AI 系统需要比较真实候选方案、形成架构决策、明确运行边界并给出可供详细设计使用的推荐结论时使用。可研、详细设计、独立评审、解释性写作和执行分别路由到其责任工作流。.

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-solution

产出可支撑决策的**技术方案、概要设计、解决方案架构和建设方案**。

## 交付物

- 技术方案文档 / 概要设计 / 解决方案架构文档
- 建设方案或设计导向的项目建设计划
- 候选方案比较矩阵
- 推荐方案及风险说明
- 重大决策的架构决策记录输入

## 执行步骤

### 1. 目标与约束确认

- 明确文档类型（技术方案 / 概要设计 / 解决方案架构 / 建设方案）
- 确认读者（决策层 / 技术团队 / 甲方评审）
- 确认约束条件：时间、预算、技术栈、合规要求
- 区分已批准约束与可在本次设计空间内改变的当前做法或候选假设
- 验证或采用在范围内时，明确其决策阶段：探索、有边界的试点、扩大采用或生产承诺。区分目标架构、下一步推荐动作与当前授权范围
- 检查是否有已有需求文档（`rd-requirement` 产出）
- 项目有立项审批阶段时，检查可研输入（`rd-feasibility` 产出）
- 从项目材料中核实可查事实，只向用户确认仍未决定且会实质影响方案的事项
- 使用既有领域术语；发现冲突时显式指出，不静默创建同义词

**完成标准：** 目标文档、受众、已批准输入、约束、重要决策阶段、未决决策和术语依据均已明确到足以生成真实候选方案；验证或采用范围不与目标架构或执行授权混淆。

### 2. 方案研究与候选生成

- 存在真实架构或技术选择时，至少生成 **2 个候选方案**
- 存在实质设计空间时，寻找具有可信收益机制、与现有路径实质不同的方法，适用时包含新兴技术或新工作流。将未验证收益标为假设，以适配和价值评价创新，仅保留有依据的候选方案
- 每个方案包含：架构概览、核心组件、数据/接口边界、技术选型、部署或运行假设
- 识别影响决策的成熟度、兼容性、政策、成本或当前版本证据缺口，并应用下方[工具选择](#工具选择)规则；候选生成不得演变为无边界搜索阶段
- 基础设施、网络、代理、VPN、VPS 或 AI 工具方案应明确建模信任边界、控制流/数据流、凭据归属、平台/版本约束、可观测性、恢复和退出路径

**完成标准：** 每项真实决策至少有两个适用于当前决策范围的可行候选方案，或记录只剩一个方案的原因；各候选方案声明同一组重要边界和假设，不把有潜力的假设表述为已确立能力。

### 3. 多维度交叉检查

对每个候选方案从以下维度评估：

| 维度 | 检查内容 |
|------|---------|
| 功能完整性 | 是否覆盖全部 P0/P1 需求 |
| 性能 | 容量规划、瓶颈预判、扩展路径 |
| 可靠性 | 容错、灾备、数据一致性策略 |
| 安全性 | 认证授权、输入校验、数据保护、审计 |
| 可维护性 | 组件责任、可观测性、运维复杂度 |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add alieismy/codex-three-layer-delivery/rd-solution@sha256:d8aaade5ef97e950

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_4nmaouewuevllvoj.svg)](https://markdownregistry.com/a/art_4nmaouewuevllvoj)

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

Versions

The registry has recorded 5 versions of this file, between Jul 31, 2026 and Oct 9, 2026, about one every 18 days.

version	committed	commit	size	audit
git:20261009.a01d3df latest	2026-10-09	a01d3df	7,978 B	A	view · diff
git:20261005.e295253	2026-10-05	e295253	7,738 B	A	view · diff
git:20260918.0060184	2026-09-18	0060184	6,488 B	A	view · diff
git:20260807.e82ae86	2026-08-07	e82ae86	6,281 B	A	view · diff
git:20260731.a8b8dd3	2026-07-31	a8b8dd3	6,165 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 (7978 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_4nmaouewuevllvoj
GET https://markdownregistry.com/api/v1/resolve?ref=alieismy/codex-three-layer-delivery/rd-solution
GET https://markdownregistry.com/api/v1/blob/d8aaade5ef97e95071431424d232623afde7b0bdd6445a3d728d69ffc12de617

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…