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

rd-requirement SKILL.md skillA

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

把原始诉求、会议纪要、干系人反馈或业务场景转化为 PRD、SRS、结构化需求或追踪材料。当产品、系统、基础设施或 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-requirement

将用户原始诉求转化为**结构化、可追溯、可验证的需求文档**。

## 交付物

- 结构化需求文档（PRD / SRS / 用户故事集）
- 用户角色与场景模型
- 干系人分析矩阵（复杂项目）
- 需求追踪矩阵（可选）
- 外部责任人确认问卷（仅在可识别的知识或决策责任人掌握阻塞性答案时使用）

## 执行步骤

### 1. 需求采集与澄清

- 区分用户原始表述和结构化需求，保留原始表述不篡改意图
- 识别隐含假设，显式列出
- 先从用户提供材料和项目中核实可查事实，再向用户提问
- 只询问需要用户决定或会阻塞决策的模糊点；高影响决策每次处理一个分支，低风险假设可显式标注后继续
- 当影响决策的事实、决定或批准由可识别的外部责任人掌握，且当前用户缺少知识或权限时，读取 [external-stakeholder-questionnaire.md](references/external-stakeholder-questionnaire.md)；只向当前用户确认接收人和需要带回的结果，不要求其代表接收人作答
- 识别含义过载或相互冲突的领域术语，提出规范术语，但不得编造业务含义
- 使用 5W1H 框架（Who / What / Why / When / Where / How）覆盖需求维度

**完成标准：** 每个影响决策的歧义均已解决，或明确归入假设、未决决策或验证动作；可从材料中查明的事实不再作为用户问题遗留，外部知识或权限缺口也具有接收角色和返回判据，而不是由代理编造答案。

### 2. 需求分类与结构化

按以下维度分类整理：

| 类别 | 内容 |
|------|------|
| 功能需求（FR） | 系统必须做什么 |
| 非功能需求（NFR） | 性能、可用性、可扩展性、安全性、兼容性 |
| 约束条件 | 技术栈、平台、法规、预算、时间 |
| 假设 | 未确认但影响设计的前提 |
| 排除项 | 明确不做的事项 |
| 运行环境 | 环境、拓扑、用户能力、支持、迁移和生命周期约束 |

面向文档型项目时，额外分类：

| 类别 | 内容 |
|------|------|
| 干系人 | 用户、业务负责人、评审方、维护方、外部主管机构 |
| 业务规则 | 政策、流程、审批、合规或运行规则 |
| 数据与接口 | 所需数据对象、外部系统、交换边界 |
| 证据来源 | 会议纪要、标准、既有文档、法规、产品决策 |

**完成标准：** 每个范围内场景均映射到已识别的角色、规则、数据或接口边界，并至少对应一项已分类需求或明确排除项。

### 3. 优先级标注

每项需求标注优先级：

- **P0（Must Have）**：不实现则项目失败
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add alieismy/codex-three-layer-delivery/rd-requirement@sha256:5f16b295807b5be2

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

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,421 B	A	view · diff
git:20260918.0060184	2026-09-18	0060184	7,275 B	A	view · diff
git:20260831.3a305d6	2026-08-31	3a305d6	7,032 B	A	view · diff
git:20260807.e82ae86	2026-08-07	e82ae86	6,365 B	A	view · diff
git:20260731.a8b8dd3	2026-07-31	a8b8dd3	6,124 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 (7421 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_qplpqqkgwu2nu2h2
GET https://markdownregistry.com/api/v1/resolve?ref=alieismy/codex-three-layer-delivery/rd-requirement
GET https://markdownregistry.com/api/v1/blob/5f16b295807b5be2ae72ea6e818da2b24dd1298bf17f6a6f8ed2fb6cca1f1daa

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…