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

rd-writing SKILL.md skillA

rd-writing 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-writing@git:20261010.408a3b4

Pins git:20261010.408a3b4 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-writing/SKILL.md
Versions recorded: 5
Latest version: git:20261010.408a3b4, committed Oct 10, 2026
First version recorded: Jul 26, 2026
Size: 5,761 bytes
Repository stars: 12
License: MIT

编写有来源支撑的技术文章、白皮书、研究或事实核查报告、决策简报和其他专业解释性文档。当已核实证据需要面向真实受众和发布/决策目的组织成文，同时保留不确定性、反方论证和追踪关系时使用。PRD、架构选型、详细设计、标准制定和独立评审分别路由到其责任工作流。.

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

将已核实材料转化为面向受众的专业文档，同时保持主张、逻辑和证据可审计。

## 交付物

- 技术文章、解释性文章或技术白皮书
- 研究综述或事实核查报告
- 决策简报、立场文件或证据导向的建议备忘录
- 重要时附主张—来源映射和未解决证据说明

## 选择输出模式

只读取目标任务需要的参考文件：

| 模式 | 目标对象 | 参考文件 |
|------|----------|----------|
| 技术文章 | 技术文章、解释性文章、技术白皮书 | [technical-article.md](references/technical-article.md) |
| 证据报告 | 研究综述、事实核查报告、证据评述 | [evidence-report.md](references/evidence-report.md) |
| 决策简报 | 决策备忘录、立场文件、高管技术简报 | [decision-brief.md](references/decision-brief.md) |

## 通用流程

### 1. 固定写作契约

- 确认受众、决策或发布目的、范围、体裁、篇幅、语气、日期边界和引用格式；存在硬性篇幅限制时，明确计数单位和纳入计数的内容
- 识别已提供来源、需要当前核实的主张，以及编辑或组织约束
- 保留既有术语、名称、日期、引语、编号和追踪关系
- 用户给出期望结论时，将其视为待检验命题，而非需要维护的事实

**完成标准：** 受众、目的、范围、模式、日期边界、来源集合、语气、篇幅和引用契约均已明确。

### 2. 建立主张结构

- 明确中心问题和候选结论
- 建立主张层级：中心主张、支持主张、证据、反方主张、限制和含义
- 区分事实、估算、推断、预测、观点和价值判断
- 删除与文档目的无关或缺乏证据的主张

**完成标准：** 每个保留主张均服务于文档目的，具有主张类型，并映射到证据、推理、反方主张、限制或明确的核验缺口。

### 3. 先核实再起草

- 先检查用户提供材料和项目来源，复用适用范围与时效仍有效的已检查证据；仅当重要主张所需证据缺失、过期、有争议或精度不足时，使用 `rd-research`
- 重要时核实时间线、版本、法域、单位、分母、引语上下文和来源所有者
- 记录冲突和证据缺口；不得让流畅文字掩盖不确定性

**完成标准：** 每项影响决策或拟发布的事实主张在起草正文前，均已按所需精度核实，或在计划措辞中明确限定。

### 4. 面向受众起草

- 除非体裁另有要求，先给答案或决策意义
- 使用最小充分结构，只在受众知识需要时解释专业术语
- 公平呈现最强重大反方论证，再进行回应
- 证据就近支持主张，并区分来源事实与作者分析
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add alieismy/codex-three-layer-delivery/rd-writing@sha256:ff1aa07d85103230

The line at the top of this page pins the label git:20261010.408a3b4, 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_dm2dgu6pvgd4uehz.svg)](https://markdownregistry.com/a/art_dm2dgu6pvgd4uehz)

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

Versions

The registry has recorded 5 versions of this file, between Jul 26, 2026 and Oct 10, 2026, about one every 19 days.

version	committed	commit	size	audit
git:20261010.408a3b4 latest	2026-10-10	408a3b4	5,761 B	A	view · diff
git:20261009.a01d3df	2026-10-09	a01d3df	5,185 B	A	view · diff
git:20260807.e82ae86	2026-08-07	e82ae86	5,072 B	A	view · diff
git:20260731.a8b8dd3	2026-07-31	a8b8dd3	4,841 B	A	view · diff
git:20260726.db4ec36	2026-07-26	db4ec36	4,071 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 (5761 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_dm2dgu6pvgd4uehz
GET https://markdownregistry.com/api/v1/resolve?ref=alieismy/codex-three-layer-delivery/rd-writing
GET https://markdownregistry.com/api/v1/blob/ff1aa07d85103230d3811eaa9cf7f1bec27627e95e56f8501933e6e26e8d4b39

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…