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

rd-feasibility SKILL.md skillA

rd-feasibility 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-feasibility@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-feasibility/SKILL.md
Versions recorded: 5
Latest version: git:20261009.a01d3df, committed Oct 9, 2026
First version recorded: Jul 26, 2026
Size: 5,873 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-feasibility

产出**可支撑决策的可研报告 / 可行性分析报告**，明确区分事实、假设、估算和待核实事项。

## 交付物

- 可研报告 / 可行性分析报告
- 可行性对比矩阵
- 结论：可行 / 有条件可行 / 不可行
- 风险登记表及缓解、核验动作

## 执行步骤

### 1. 研究范围确认

- 明确决策问题：要判断什么是否可行
- 决策阶段会改变所需证据时，明确当前属于探索、有边界的试点、扩大采用还是生产承诺
- 明确读者：决策层、立项评审委员会、甲方评审、技术负责人
- 确认输入：PRD、会议纪要、既有系统文档、标准、政策、预算、周期
- 评估前先区分事实和假设

**完成标准：** 决策问题、相关决策阶段、比较范围、受众、来源集合、事实、假设和证据缺口均已明确。

### 2. 可行性维度

按以下维度评估项目或方案：

| 维度 | 检查内容 |
|------|----------|
| 必要性与机会 | 问题价值、政策/业务驱动、干系人需求、潜在收益，以及延迟行动或沿用现状的成本 |
| 技术可行性 | 技术成熟度、兼容性、集成约束、数据可得性、架构适配 |
| 经济可行性 | 预算、全生命周期成本、许可、人员、采购 |
| 进度可行性 | 里程碑、依赖关系、评审周期、交付风险 |
| 运行可行性 | 可安装性、可维护性、人员配置、流程适配、培训、支持和回退 |
| 安全与合规 | 法规、标准、隐私、供应链暴露、安全控制、可审计性 |
| 可持续性 | 上游维护、发布节奏、许可、厂商或社区依赖、未来演进、学习价值和退出路径 |
| 风险可行性 | 高风险假设、外部依赖、失败模式、替代路径 |

**完成标准：** 每个重要维度均依据证据完成评价，或说明理由后明确排除；未覆盖维度不得被静默视为有利。

### 3. 候选方案

- 存在真实选择时至少比较 2 个方案
- 适用时包含“维持现状”作为基线方案
- 按与新方案相同的标准评估现状基线的成本和风险；区分有潜力的假设与已有证据支持进入拟议阶段的方案
- 详细比较前先说明被排除方案及排除理由
- 不把单一偏好方案包装成唯一可行方案

**完成标准：** 每个真实候选方案和相关现状基线均按共同准则比较，或有明确记录的排除依据。

### 4. 证据与估算纪律

- 事实性结论、时效性资料、标准、政策、市场或成本数据必须标注来源
- 区分可检索事实和责任人决策，并记录每项已接受条件或风险的决策权限
- 估算必须标注为估算，并说明估算依据
- 精确数据不可得时，用范围和敏感性分析替代伪精确数字
- 对无法证实的假设单独列出核验方法
- 对开源或 AI 工具选型，区分仓库活跃度与可维护性、演示与可复现能力、模型能力与产品/系统能力
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add alieismy/codex-three-layer-delivery/rd-feasibility@sha256:a14d5603e96f500c

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

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 9, 2026, about one every 19 days.

version	committed	commit	size	audit
git:20261009.a01d3df latest	2026-10-09	a01d3df	5,873 B	A	view · diff
git:20261005.e295253	2026-10-05	e295253	5,735 B	A	view · diff
git:20260807.e82ae86	2026-08-07	e82ae86	4,898 B	A	view · diff
git:20260731.a8b8dd3	2026-07-31	a8b8dd3	4,702 B	A	view · diff
git:20260726.db4ec36	2026-07-26	db4ec36	3,995 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 (5873 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_w5ggrnhajuqpjvei
GET https://markdownregistry.com/api/v1/resolve?ref=alieismy/codex-three-layer-delivery/rd-feasibility
GET https://markdownregistry.com/api/v1/blob/a14d5603e96f500c3a7a819b92d00a2119a57953811e483bf067dca724847009

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…