ontology-driven-dev SKILL.md skillA

ontology-driven-dev from sharptoolbox/ontology-driven-dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add sharptoolbox/ontology-driven-dev/ontology-driven-dev@git:20260830.3068cd1

Pins git:20260830.3068cd1 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
sharptoolbox/ontology-driven-dev
Path
SKILL.md
Versions recorded
1
Latest version
git:20260830.3068cd1, committed Aug 30, 2026
Size
11,414 bytes
Repository stars
478
License
MIT

当用户要基于业务需求,通过「需求探索 → 本体建模 → 应用构建」三步法开发一套完整、可运行的本体驱动 BS(浏览器前后端) 业务系统时使用。基于七模型本体 YAML(M1/M2/M3/M5/M6/M7/MU) 与内置 code-paas 技术底座,强制每个需求探索阶段人工确认,产出严格对齐需求文档、本体模型与代码的系统。支持整体触发与单阶段入口(仅建模/仅构建)。触发词含:本体驱动、需求探索、本体建模、七模型、code-paas、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

# 本体驱动系统开发技能(Ontology-Driven Dev)

将"业务需求 → 软件需求规格 → 七模型本体 YAML → 可运行 BS 系统"的完整方法论打包为可复用技能。
技术底座为内置的 `code-paas`(Flask + SQLite + React/TS 单体应用,含系统管理、流程引擎、工作台、本体注册表),
输出严格受四份规范约束。

> **路径约定(跨工具通用)**:本技能内所有相对路径(如 `references/`、`reference-example/`、`techbase/`)均以「**本 SKILL.md 所在文件夹**」为根目录。
> - WorkBuddy / Claude Code / Codex 等工具在加载技能时会自动解析该根目录;
> - 若某工具未自动解析,请将下文 `<本技能目录>` / `<技能根目录>` 占位符替换为本 SKILL.md 的**绝对路径**(例如 `C:\Users\hemin\.claude\skills\ontology-driven-dev` 或 `~/.workbuddy/skills/ontology-driven-dev`)后执行。

## 一、适用场景与触发

- 用户给出一段业务需求(一句话或一段描述),希望产出一套可运行业务系统。
- 用户明确要求"需求探索确认 / 本体建模 / 七模型 / 基于 code-paas 构建 / AI 原生应用"。
- 自然语言示例:「帮我开发一个 XX 管理系统」「把这段需求做成本体驱动开发」「基于这份需求规格说明书生成系统」。

## 二、三阶段管线 + 人工门禁(强顺序)

阶段一与阶段二、阶段三之间强顺序;阶段一内部八阶段也强顺序,且每一阶段都必须**人工确认**后才可推进。

### 阶段一:需求探索 → 软件需求规格说明书

- **唯一依据**:`references/AI需求探索与确认提示词V9.0.md`(其附录一即《软件需求编写规范 V9.0》全文,是本阶段格式 / 编号 / 图表 / 自检的唯一基准)。
- **严格按该提示词的"阶段零 ~ 阶段七"八阶段推进**:
  - 阶段零 总体理解确认 → 阶段一 业务对象 → 阶段二 业务功能与规则 → 阶段三 跨对象联动识别 →
    阶段四 端到端协同流与审批流 → 阶段五 查询统计与固定报表 → 阶段六 角色权限 → 阶段七 UI 原型(可选,须先确认是否需要)。
- **人工确认门禁(强制,不可跳过)**:每个阶段(stage0-7)结束、进入下一阶段前,必须按提示词统一的"问题 N + AI建议 + 建议理由 + 其他选项 + 快捷回复"格式提问,并**硬性暂停等待用户明确确认**("按AI建议" / 选项字母 / 修改意见)后才可推进。
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add sharptoolbox/ontology-driven-dev/ontology-driven-dev@sha256:62fc08e3d96edc96

The line at the top of this page pins the label git:20260830.3068cd1, 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 badge

[![mdr](https://markdownregistry.com/badge/art_hzlfixm2ypw6guqo.svg)](https://markdownregistry.com/a/art_hzlfixm2ypw6guqo)

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

Versions

The registry has recorded 1 version of this file, committed on Aug 30, 2026.

versioncommittedcommitsizeaudit
git:20260830.3068cd1 latest2026-08-30 3068cd1 11,414 BA 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 (11414 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

sharptoolbox/ontology-driven-dev · 478 stars · license MIT · pushed 2026-10-09 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_hzlfixm2ypw6guqo
GET https://markdownregistry.com/api/v1/resolve?ref=sharptoolbox/ontology-driven-dev/ontology-driven-dev
GET https://markdownregistry.com/api/v1/blob/62fc08e3d96edc960db861ca41be199c3ac598c350574b96ad0025277e57bc0e

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.

Browse by kind, by grade A, or by owner.