spec-direction-gate SKILL.md skillA

spec-direction-gate from chenweil/skillcaddy is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add chenweil/skillcaddy/spec-direction-gate@git:20260930.87567b6

Pins git:20260930.87567b6 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
chenweil/skillcaddy
Path
skills/spec-pipeline/spec-direction-gate/SKILL.md
Versions recorded
1
Latest version
git:20260930.87567b6, committed Sep 30, 2026
Size
6,098 bytes
Repository stars
30
License
MIT

技术方案文档的方向确认关卡。在 specs/<id>/TECH.md 草稿完成、进入实施之前,先确认方向、再确认内容,两次确认分开且有序;把关卡结论写回 TECH.md 作为批准状态的显式记录。拒绝语义:没有人在场就停止并报告,绝不自动放行。用于任何"文档获批才能开始写代码"的环节之前。.

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

# 方向确认关卡(B)

一条流程只有在"方向"这一格真的会挡住它的时候才算成立。这个技能就是那一格。

输入是 `specs/<id>/TECH.md` 的草稿,输出是写回 `TECH.md` 的批准状态记录。中间没有任何自动放行的路径。

## 何时使用

- `TECH.md` 草稿已写完,尚未开始实施
- 需要在实施前留下"谁在什么时候批准了方向"的可核验记录
- 复盘时需要确认某个实施是否真的经过方向批准,而不是默认通过

## 何时不使用

- 纯 UI 改动、单文件修复等低复杂度变更,`TECH.md` 本身就不必产出
- 方向已经单独确认过、这次只是修订若干小节时,改用下面的"增量修订"路径

## 硬性约束

1. **两次确认,不合并。** 先确认方向,确认通过之后才确认内容。合并这一步会破坏关卡:把大纲和方向放在同一次确认里,人会锚定在已经看到的具体大纲上,而不再重新考虑它上位的那个问题。
2. **拒绝语义。** 没有人在场就停止并报告这个技能需要人,不要"先按草稿往下走,回头再确认"。
3. **批准要落盘。** 两次确认的结论写进 `TECH.md`,不只留在对话里。实施阶段的验收要能读到"批准后文档仍存活"的证据。
4. **批准的是方向,不是逐字内容。** 方向确认通过后,作者仍可改实现细节;实施者不得改方向。

## 流程

### 第 0 步:确认在场

先确认当前是有人可以回答的交互会话。

不是交互式会话时:**停下并报告**"这个关卡需要人在场确认方向",然后结束。不要用默认值代替确认,也不要因为草稿看起来已经足够好就跳过。

### 第 1 步:确认方向

读 `TECH.md`,然后只向人提出**方向层面**的问题,不要展示具体大纲或章节结构:

- 这份文档要解决的问题,和仓库当前状态对得上吗
- 选定的方案,是这几个候选里最合适的那个吗
- 哪些明确不在这次范围内
- 还有什么上位问题,是这份文档答不了的

把问题一次问完,然后等回答。

**方向被拒时的处理**:记录被拒的方向和原因,停止。不要改写成新的大纲再问第二遍——那等于把第一次确认作废。修改草稿后必须从第 1 步重来。

### 第 2 步:确认内容

只有在第 1 步通过后才进入这一步。展示文档的实际章节和每节承担的内容,然后等确认。

内容被拒时:按意见修订,同样从第 1 步重新开始(内容修订可能改变方向)。

### 第 3 步:写回批准状态

两次都通过后,把结论追加到 `TECH.md` 末尾:

```markdown
## Approval

- 方向确认:通过 / 拒绝(时间:YYYY-MM-DD HH:MM CST,确认人:__)
- 内容确认:通过 / 拒绝(时间:YYYY-MM-DD HH:MM CST,确认人:__)
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add chenweil/skillcaddy/spec-direction-gate@sha256:eaa7cf2333d73047

The line at the top of this page pins the label git:20260930.87567b6, 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_euxfjb7vmsvsxrhb.svg)](https://markdownregistry.com/a/art_euxfjb7vmsvsxrhb)

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

Versions

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

versioncommittedcommitsizeaudit
git:20260930.87567b6 latest2026-09-30 87567b6 6,098 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 (6098 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

chenweil/skillcaddy · 30 stars · license MIT · pushed 2026-10-30 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_euxfjb7vmsvsxrhb
GET https://markdownregistry.com/api/v1/resolve?ref=chenweil/skillcaddy/spec-direction-gate
GET https://markdownregistry.com/api/v1/blob/eaa7cf2333d730479d76a439571f963f131f208dde354b995c9a698ade4eb8ec

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 chenweil/skillcaddy

AGENTS.md AGENTS.md file
chenweil/skillcaddy · AGENTS.md
git:20261023.7e5866f · audit A · 30 stars
skillcaddy-manager SKILL.md skill
chenweil/skillcaddy · skills/skillcaddy-manager/SKILL.md · Manage Skillcaddy source acquisition, source updates, migrations, project skill links, and the Web/TUI CLI. Use for…
git:20260817.a910e91 · audit B · 30 stars
spec-draft-intake SKILL.md skill
chenweil/skillcaddy · skills/spec-pipeline/spec-draft-intake/SKILL.md · 外部模型草稿的摄入关卡。把下载的外部技术方案草稿当作不可信输入,逐条与仓库实际状态对账,产出一份经审的 specs/<id>/TECH.md。草稿是候选不是权威:不因草稿存在而跳过研究,也不把草稿的断言直接升格为文档结论。用于"外部模型写了…
git:20260930.87567b6 · audit A · 30 stars
spec-role-contract SKILL.md skill
chenweil/skillcaddy · skills/spec-pipeline/spec-role-contract/SKILL.md · 技术方案文档的角色契约。把作者 / 实施者 / 验证者三个文档生命周期位置写成显式参数,规定每个位置的可做与不可做,并用落盘的角色记录让边界可核验。与模型品牌解耦——换模型不改变角色边界,同一模型跑不同角色也照样受约束。用于"这份文档现在归…
git:20260930.87567b6 · audit A · 30 stars

Every file in chenweil/skillcaddy

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