@captain_z/zsk-skills 1.8.8 → 1.8.10

package/README.md

@@ -2,20 +2,20 @@
 
 ZNorth Standard Kit 的可安装 skill 内容包。安装面现在只保留从根级 `skills/` 生成的 **core harness-first skills**；旧 `.best-practices/` 不再批量生成独立 installable skills，而是作为参考源按 skill 携带相关子集。
 
-包内共有 **24 颗 installable skills**，全部来自根级 `skills/`。
+包内共有 **26 颗 installable skills**，全部来自根级 `skills/`。其中 legacy full-core profile 继续保留 24 颗生命周期 skill；`check` / `health` 是可选诊断能力，适合通过 custom、单颗安装或 GitHub skill 管理器引入。
 
 ## 合规审查（ARCHITECTURE §4.4 硬指标）
 
 | 检查项                                                                                   | 结果    | 说明                                                  |
 | ---------------------------------------------------------------------------------------- | ------- | ----------------------------------------------------- |
-| frontmatter 完整（`name` / `description` / `category` / `domain` / `tier` / `triggers`） | ✓ 24/24 | core 由 root `skills/` 生成 |
-| `name` 使用裸 slug，扁平且不含连字符                                                       | ✓ 24/24 | LLM 原生 skill 入口保持简洁；CLI 选择层使用 `zsk:<slug>` |
-| `description` 简洁表达职责和使用时机                                                       | ✓ 24/24 | 面向索引阅读；triggers 留给机器使用 |
-| `category` / `domain` / `tier` 枚举值合法                                                | ✓ 24/24 | stage/utility · core |
-| `triggers` 数组非空                                                                      | ✓ 24/24 | 至少含裸 slug |
+| frontmatter 完整（`name` / `description` / `category` / `domain` / `tier` / `triggers`） | ✓ 26/26 | core 由 root `skills/` 生成 |
+| `name` 使用公共命名，目录同名且只含小写/数字/连字符                         | ✓ 26/26 | 主入口为 `zskplan` / `zsk`；其它 skill 使用 `zsk-<slug>` 避免裸名冲突；CLI 选择层继续兼容 `zsk:<slug>` |
+| `description` 简洁表达职责和使用时机                                                       | ✓ 26/26 | 面向索引阅读；triggers 留给机器使用 |
+| `category` / `domain` / `tier` 枚举值合法                                                | ✓ 26/26 | stage/utility · core |
+| `triggers` 数组非空                                                                      | ✓ 26/26 | 至少含裸 slug |
 | 无硬编码项目名 / 技术栈（统一 `{{config.*}}` 占位符）                                    | ✓       | harness-neutral                                       |
 | `related:` 相对路径合法                                                                  | ✓       | core 不依赖参考层生成物                               |
-| 单文件 ≤ 300 行                                                                          | ✓ 24/24 | core 由 `lint:harness` 强制                           |
+| 单文件 ≤ 300 行                                                                          | ✓ 26/26 | core 由 `lint:harness` 强制                           |
 
 当前 `max-lines` 已由 `tools/lint-frontmatter.ts` 作为 error 强制；新增或修改 skill 不应超过 300 行。
 
@@ -35,10 +35,10 @@ Profile 是流程组合策略，不是新的 skill。Atomic skills 仍然平铺
 | profile | skills | 适用场景 |
 | --- | ---: | --- |
 | `zsk-entry` | 2 | 只装 `zskplan` / `zsk` 两个主入口，由它们按 harness 调度 |
-| `zsk-lite` | 11 | 小修、小项目、脚本、低风险任务 |
-| `zsk-sdlc` | 21 | 标准工程交付；需求、实现、审查、验证、验收、归档 |
-| `zsk-frontend` | 22 | UI/UX/browser-facing 交付；强化 demo、视觉证据、前端质量门禁 |
-| `zsk-enterprise` | 22 | 高治理交付；要求 deploy、验收、归档、审计证据 |
+| `zsk-lite` | 4 | 小修、小项目、脚本、低风险任务；只暴露入口和 coding/verify |
+| `zsk-sdlc` | 12 | 标准工程交付；安装入口 + 一等阶段，capability/gate 由 workflow 调度 |
+| `zsk-frontend` | 13 | UI/UX/browser-facing 交付；基于 SDLC 阶段面加装 demo |
+| `zsk-enterprise` | 12 | 高治理交付；deploy/audit/review 由 profile gate/capability 开启 |
 | `sdlc-only` | 24 | 旧入口兼容；安装全部 core skills |
 
 ## Skill 搭配流程图
@@ -85,24 +85,27 @@ Direct review 只需要明确 review target（代码 diff、本地路径、stage
 | --- | --- | --- |
 | 安装默认 core skills | `npx @captain_z/zsk add` | 交互选择 target 和 bundle |
 | CI 安装 ZSK 主入口 | `npx @captain_z/zsk add zsk-entry --target=~/.claude/skills --yes` | 非交互安装 `zskplan` / `zsk` 两个入口 |
-| CI 安装轻量 profile | `npx @captain_z/zsk add zsk-lite --target=~/.claude/skills --yes` | 非交互安装 11 颗常用 skills |
-| CI 安装标准 SDLC profile | `npx @captain_z/zsk add zsk-sdlc --target=~/.claude/skills --yes` | 非交互安装 21 颗标准 workflow skills |
-| Claude plugin 安装 | `/plugin marketplace add codeshareman/zsk` 后 `/plugin install zsk@zsk` | 使用 `/zsk:<slug>` 命令面 |
-| GitHub skills 管理器安装 | `npx skills add codeshareman/zsk` | 从仓库根 `skills/` 安装；不要加 `@` |
+| CI 安装轻量 profile | `npx @captain_z/zsk add zsk-lite --target=~/.claude/skills --yes` | 非交互安装 4 颗入口/执行 skills |
+| CI 安装标准 SDLC profile | `npx @captain_z/zsk add zsk-sdlc --target=~/.claude/skills --yes` | 非交互安装 12 颗标准 entry/stage skills |
+| Claude plugin 分层安装 | `/plugin marketplace add codeshareman/zsk` 后 `/plugin install zsk-entry@zsk` | 在 Claude 内按 profile 安装 ZSK skills |
+| Claude plugin 全量兼容 | `/plugin install zsk@zsk` | 安装 24 颗 core skills，保留给旧工作流或高级用法 |
+| GitHub skills 管理器安装 | `npx skills add codeshareman/zsk` | 从仓库安装公共命名的 ZSK skills 或单颗 skill；不要加 `@` |
+| Skill 质量 dry-run | `npx @captain_z/zsk skills dry-run --min-score=90` | 不调用 LLM、不写项目；模拟每颗 skill 的输入、输出、质量检查、stop condition 和专属场景断言；总分、`qualityItems[]` 和 `scenarioChecks[]` 单项都必须达到阈值 |
 | 准备项目资源 | `npx @captain_z/zsk prepare draft && npx @captain_z/zsk prepare plan && npx @captain_z/zsk prepare sync --all` | 先审查建议，再同步确认后的 `.zsk/raws/**` snapshot |
-| 只想让 ZSK 自己规划和执行 | "用 `zsk:zskplan` 规划" / "用 `zsk:zsk` 继续" | 计划写入 `.zsk/plans/`，执行产物写入 `.zsk` |
+| 只想让 ZSK 自己规划和执行 | "用 `zskplan` 规划" / "用 `zsk` 继续" | 计划写入 `.zsk/plans/`，执行产物写入 `.zsk` |
 | 不确定该用哪个阶段 skill | "用 `zsk:dispatch` 调度" | 让 OMX 围绕 ZSK skills 分配 subagents |
 | 恢复一个项目的下一步 | "用 `zsk:flow` 继续" | 读取配置、阶段文档和 blocker，选择合法下一阶段 |
 | 明确进入某阶段 | "用 `zsk:spec` 写模块规格" | 只载入对应 stage contract |
 
-**典型消费路径**（production，安装后）：
+**典型消费路径**（production，安装后）。`<public-name>` 表示 `zskplan` / `zsk` 两个裸入口，或其它 skill 的 `zsk-<slug>`：
 
-- `~/.claude/skills/zsk-<slug>/SKILL.md` — Claude Code / flat target
-- `~/.codex/skills/zsk-<slug>/SKILL.md` — Codex / flat target
+- `~/.claude/skills/<public-name>/SKILL.md` — Claude Code / flat target
+- `~/.codex/skills/<public-name>/SKILL.md` — Codex / flat target
 - `./.claude-plugin/skills/<slug>/SKILL.md` + `commands/<slug>.md` — Claude plugin local target
-- `@captain_z/zsk-skills/<slug>/SKILL.md` — 通过 npm 读
+- `skills/.curated/<public-name>/SKILL.md` — `npx skills` / Claude plugin marketplace repository target
+- `@captain_z/zsk-skills/<public-name>/SKILL.md` — 通过 npm 读
 
-仓库根还发布 `.claude-plugin/plugin.json` 和 `.claude-plugin/marketplace.json`，用于 Claude Code `/plugin marketplace add codeshareman/zsk` + `/plugin install zsk@zsk`；根级 `skills/` 同时兼容 `npx skills add codeshareman/zsk`。
+仓库根还发布 `.claude-plugin/plugin.json` 和 `.claude-plugin/marketplace.json`，用于 Claude Code `/plugin marketplace add codeshareman/zsk` 后按 profile 安装 `zsk-entry@zsk`、`zsk-lite@zsk`、`zsk-sdlc@zsk`、`zsk-frontend@zsk` 或 `zsk-enterprise@zsk`；`zsk@zsk` 保留为全量兼容入口。根级 `skills/.curated/` 同时兼容 `npx skills add codeshareman/zsk`。
 
 ## 和项目知识工作区的关系
 
@@ -118,28 +121,28 @@ Skills 负责更需要判断的部分：理解已同步的 SRS、PRD、API 契
 
 | 领域              | skill 数 | 职责                                       |
 | ----------------- | -------- | ------------------------------------------ |
-| `skills/`         | 24       | harness-first 默认工作流入口               |
-| **总计**          | **24**   |                                            |
+| `skills/`         | 26       | harness-first 默认工作流入口与可选诊断能力 |
+| **总计**          | **26**   |                                            |
 
 ## 安装套件（bundles.yaml）
 
 | name                           | skills | 场景                                          |
 | ------------------------------ | ------ | --------------------------------------------- |
 | `zsk-entry`                    | 2      | 只安装 ZSK / ZSK Plan 两个主入口 |
-| `zsk-lite`                     | 11     | 小型低风险任务；ZSK 入口 + fix/coding → smoke → review → commit |
-| `zsk-sdlc`（推荐）             | 21     | 标准工程交付；完整需求、实现、审查、验证、验收、归档链路 |
-| `zsk-frontend`                 | 22     | 前端/视觉/browser-facing 任务；强化 demo 和前端质量门禁 |
-| `zsk-enterprise`               | 22     | 高治理交付；要求 deploy、验收、归档、审计证据 |
+| `zsk-lite`                     | 4      | 小型低风险任务；入口 + coding/verify，review/smoke/commit 作为 workflow capability |
+| `zsk-sdlc`（推荐）             | 12     | 标准工程交付；安装入口 + 一等阶段 |
+| `zsk-frontend`                 | 13     | 前端/视觉/browser-facing 任务；强化 demo 和 evidence |
+| `zsk-enterprise`               | 12     | 高治理交付；deploy/audit/review 由 profile gate/capability 开启 |
 | `sdlc-only`                    | 24     | 旧入口兼容；安装全部 core skills |
 | `frontend-project`             | 24     | 旧入口兼容；推荐改用 `zsk-frontend` |
 | `frontend-with-design-handoff` | 24     | 旧入口兼容；推荐改用 `zsk-frontend` |
 | `custom`                       | 交互   | 通过 `zsk add` 任意多选                       |
 
-<!-- Auto-generated by tools/catalog.ts — do not edit manually. Total: 24 skills -->
+<!-- Auto-generated by tools/catalog.ts — do not edit manually. Total: 26 skills -->
 
 ## Skill 清单（core skills）
 
-> 内容由 `tools/catalog.ts` 从 `packages/skills/*/SKILL.md` frontmatter 生成。重生成：`pnpm catalog`。
+> 内容由 `tools/catalog.ts` 从 `packages/skills/<public-name>/SKILL.md` frontmatter 生成；`zsk` / `zskplan` 为裸入口，其它 skill 使用 `zsk-<slug>`。重生成：`pnpm catalog`。
 > 默认 profile bundles 只安装 entry 和保留的一等 stage；capability / gate / mode 由 `zskplan` / `zsk` 内部调度或通过 custom/legacy 明确安装。Legacy aliases 仍保留 24 个 skill 以兼容旧安装。
 
 ### Entry Skills (2)
@@ -156,81 +159,87 @@ Skills 负责更需要判断的部分：理解已同步的 SRS、PRD、API 契
 
 有独立产物边界、质量门禁和下游消费关系的一等阶段。
 
-- **`prepare`** · type: capability · keep-stage
+- **`zsk-prepare`** · type: capability · keep-stage
   After project init, collects resource origins, snapshots evidence, and updates config/manifests before proposal/spec.
 
-- **`preproposal`** · type: capability · keep-stage
+- **`zsk-preproposal`** · type: capability · keep-stage
   Before proposal, turns a one-sentence or vague intake brief into a clear, reviewed product, roadmap, UX, and readiness raw resource pack.
 
-- **`proposal`** · type: capability · keep-stage
+- **`zsk-proposal`** · type: capability · keep-stage
   Before spec, frames the problem, scope, non-goals, success criteria, stakeholders, risks, and resource gaps.
 
-- **`spec`** · type: capability · keep-stage
+- **`zsk-spec`** · type: capability · keep-stage
   After proposal, defines sourced FR/NFR, acceptance criteria, scenarios, edge cases, and open gaps.
 
-- **`design`** · type: capability · keep-stage
+- **`zsk-design`** · type: capability · keep-stage
   After spec freeze, maps behavior to interfaces, data flow, rollout plan, risks, and implementation surfaces.
 
-- **`task`** · type: capability · keep-stage
+- **`zsk-task`** · type: capability · keep-stage
   After design approval, creates executable tasks with dependencies, FR/AC coverage, owners, and evidence hooks.
 
-- **`coding`** · type: capability · keep-stage
+- **`zsk-coding`** · type: capability · keep-stage
   For approved tasks, implements small scoped diffs with tests, evidence, and blocker reporting.
 
-- **`demo`** · type: capability · keep-stage
+- **`zsk-demo`** · type: capability · keep-stage
   Before formal testing, runs planned demos and captures evidence without making acceptance claims.
 
-- **`verify`** · type: capability · keep-stage
+- **`zsk-verify`** · type: capability · keep-stage
   Independently verifies fixes or acceptance criteria against a stated claim, target version, and linked evidence.
 
-- **`acceptance`** · type: capability · keep-stage
+- **`zsk-acceptance`** · type: capability · keep-stage
   After independent verify passes, records accept/reject decision, linked evidence, and residual-risk owner.
 
-- **`archive`** · type: capability · keep-stage
+- **`zsk-archive`** · type: capability · keep-stage
   After acceptance, closes the iteration by preserving artifacts, decisions, issues, and learning proposals.
 
-### Capabilities (6)
+### Capabilities (7)
 
 可被多个阶段复用的内部能力；默认由入口或阶段调度。
 
-- **`dispatch`** · type: workflow · downshift-to-capability
+- **`zsk-dispatch`** · type: workflow · downshift-to-capability
   At task intake, asks OMX to assign subagents to the right zsk skill from request, state, evidence, and blockers.
 
-- **`review`** · type: capability · downshift-to-capability
+- **`zsk-review`** · type: capability · downshift-to-capability
   After smoke or explicit path targeting, reviews implementation or local targets against scope, contracts, evidence, security, maintainability, and ZSK boundaries.
 
-- **`defect`** · type: capability · downshift-to-capability
+- **`zsk-defect`** · type: capability · downshift-to-capability
   After formal QA reports findings, normalizes defects with repro, evidence, FR/AC links, and fix routing.
 
-- **`deploy`** · type: capability · downshift-to-capability
+- **`zsk-deploy`** · type: capability · downshift-to-capability
   After review, deploys to non-production or demo targets with version, smoke evidence, and rollback owner.
 
-- **`learn`** · type: capability · downshift-to-capability
+- **`zsk-learn`** · type: capability · downshift-to-capability
   Use after repeated friction or supplied public skill/harness references to learn, compare, record gaps, and prepare one reviewed ZSK optimization batch.
 
-- **`issue`** · type: utility · keep-capability
+- **`zsk-issue`** · type: utility · keep-capability
   Tracks defects, blockers, questions, and risks with taxonomy, severity, owner, reproduction, and evidence.
 
-### Gates (3)
+- **`zsk-health`** · type: capability · keep-capability
+  Use when auditing ZSK agent, skill, workflow, harness, and installation health to find coupling, token waste, trigger overlap, stale generated surfaces, and output-quality gaps without owning product delivery.
+
+### Gates (4)
 
 阶段内部的质量检查点或发布检查点。
 
-- **`smoke`** · type: capability · downshift-to-gate
+- **`zsk-smoke`** · type: capability · downshift-to-gate
   After coding, proves changed behavior locally with targeted tests and relevant lint/typecheck/build evidence.
 
-- **`commit`** · type: capability · downshift-to-gate
+- **`zsk-commit`** · type: capability · downshift-to-gate
   After smoke and review pass, prepares a scoped commit with intent, evidence, and clean staging.
 
-- **`ready`** · type: capability · downshift-to-gate
+- **`zsk-ready`** · type: capability · downshift-to-gate
   Before independent verification, prepares a handoff with issue mappings, evidence, version, and regression notes.
 
+- **`zsk-check`** · type: capability · downshift-to-gate
+  Before commit, push, release, or handoff, runs a lightweight readiness preflight over local changes and reports evidence, risks, and a clear ready/not-ready verdict without owning workflow gates.
+
 ### Modes (2)
 
 入口或阶段内部的执行模式。
 
-- **`flow`** · type: workflow · downshift-to-mode
+- **`zsk-flow`** · type: workflow · downshift-to-mode
   Starts or resumes delivery by reading state, resources, and blockers, then selecting the next legal stage.
 
-- **`fix`** · type: workflow · downshift-to-mode
+- **`zsk-fix`** · type: workflow · downshift-to-mode
   For persisted issues, diagnoses root cause, applies the smallest scoped correction, adds a regression guard, updates the issue, and hands off verification.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@captain_z/zsk-skills",
-  "version": "1.8.8",
+  "version": "1.8.10",
   "description": "ZNorth Standard Kit — core harness-first skill content package",
   "license": "MIT",
   "files": [

package/zsk/SKILL.md

@@ -23,7 +23,7 @@ useWhen:
   - "Use when the workflow is ready for this responsibility: Use as the
     ZSK-aware Ralph-style execution loop that follows ZSK plans, dispatches
     expert lanes, verifies, fixes, and writes only .zsk outputs."
-  - Use when the user invokes zsk:zsk or asks for zsk workflow outputs after
+  - Use when the user invokes zsk or asks for zsk workflow outputs after
     prerequisites are present.
 doNotUseWhen:
   - Do not use when required inputs, prior-stage evidence, or configured sources
@@ -31,12 +31,12 @@ doNotUseWhen:
   - Do not use to bypass stage gates, perform another skill's responsibility, or
     make unsupported completion claims.
 positiveExamples:
-  - Run zsk:zsk with the required inputs and produce the documented zsk workflow
+  - Run zsk with the required inputs and produce the documented zsk workflow
     artifacts.
   - Continue the workflow at zsk workflow after the prerequisite evidence and
     blockers are resolved.
 negativeExamples:
-  - Use zsk:zsk to skip missing prerequisites or hide unresolved blockers.
+  - Use zsk to skip missing prerequisites or hide unresolved blockers.
   - Run zsk workflow for generic chat, unrelated implementation, or another ZSK
     stage's work.
 ---

package/zsk/harness/best-practices/sdlc.md

@@ -17,7 +17,7 @@ triggers:
 
 # SDLC Reference
 
-默认执行不从这里开始，而是从根级 `skills/flow/SKILL.md` 和各 core `skills/*/SKILL.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
+默认执行不从这里开始，而是从根级 `skills/flow/SOURCE.md` 和各 core `skills/*/SOURCE.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
 
 ## 阶段边界
 

package/zsk/harness/contracts/skill-classification.yaml

@@ -211,6 +211,17 @@ skills:
     rationale: Proves changed behavior locally but usually checks an implementation rather than producing a standalone phase artifact.
     migration: Move under quality gates for coding/demo/release flows.
 
+  check:
+    currentInstallKind: workflow-node
+    currentCategory: stage
+    skillType: capability
+    targetPrimary: gate
+    disposition: downshift-to-gate
+    facets: [quality-assessment, evidence, release]
+    stageEligible: false
+    rationale: Runs lightweight readiness preflight over local changes or explicit targets without owning review, verify, approval, commit, or release.
+    migration: Keep as an optional preflight capability/gate selected by workflow profiles or direct user requests.
+
   review:
     currentInstallKind: workflow-node
     currentCategory: stage
@@ -364,3 +375,14 @@ skills:
     stageEligible: true
     rationale: Learning feedback can become a stage in learning workflows but is usually reusable governance capability after archive/review.
     migration: Keep as learning capability with stage eligibility for explicit learning optimization workflows.
+
+  health:
+    currentInstallKind: workflow-node
+    currentCategory: stage
+    skillType: capability
+    targetPrimary: capability
+    disposition: keep-capability
+    facets: [quality-assessment, documentation-feedback]
+    stageEligible: false
+    rationale: Diagnoses skill, workflow, harness, generated-surface, and install health to reduce coupling and token waste without owning product delivery.
+    migration: Keep as an optional diagnostic capability selected by maintainers, workflows, or direct troubleshooting prompts.

package/{acceptance → zsk-acceptance}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: acceptance
+name: zsk-acceptance
 description: After independent verify passes, records accept/reject decision,
   linked evidence, and residual-risk owner.
 kind: workflow-node

package/{dispatch → zsk-acceptance}/harness/best-practices/sdlc.md

@@ -17,7 +17,7 @@ triggers:
 
 # SDLC Reference
 
-默认执行不从这里开始，而是从根级 `skills/flow/SKILL.md` 和各 core `skills/*/SKILL.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
+默认执行不从这里开始，而是从根级 `skills/flow/SOURCE.md` 和各 core `skills/*/SOURCE.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
 
 ## 阶段边界
 

package/{acceptance → zsk-acceptance}/harness/contracts/skill-classification.yaml

@@ -211,6 +211,17 @@ skills:
     rationale: Proves changed behavior locally but usually checks an implementation rather than producing a standalone phase artifact.
     migration: Move under quality gates for coding/demo/release flows.
 
+  check:
+    currentInstallKind: workflow-node
+    currentCategory: stage
+    skillType: capability
+    targetPrimary: gate
+    disposition: downshift-to-gate
+    facets: [quality-assessment, evidence, release]
+    stageEligible: false
+    rationale: Runs lightweight readiness preflight over local changes or explicit targets without owning review, verify, approval, commit, or release.
+    migration: Keep as an optional preflight capability/gate selected by workflow profiles or direct user requests.
+
   review:
     currentInstallKind: workflow-node
     currentCategory: stage
@@ -364,3 +375,14 @@ skills:
     stageEligible: true
     rationale: Learning feedback can become a stage in learning workflows but is usually reusable governance capability after archive/review.
     migration: Keep as learning capability with stage eligibility for explicit learning optimization workflows.
+
+  health:
+    currentInstallKind: workflow-node
+    currentCategory: stage
+    skillType: capability
+    targetPrimary: capability
+    disposition: keep-capability
+    facets: [quality-assessment, documentation-feedback]
+    stageEligible: false
+    rationale: Diagnoses skill, workflow, harness, generated-surface, and install health to reduce coupling and token waste without owning product delivery.
+    migration: Keep as an optional diagnostic capability selected by maintainers, workflows, or direct troubleshooting prompts.

package/{archive → zsk-archive}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: archive
+name: zsk-archive
 description: After acceptance, closes the iteration by preserving artifacts,
   decisions, issues, and learning proposals.
 kind: workflow-node

package/{archive → zsk-archive}/harness/best-practices/sdlc.md

@@ -17,7 +17,7 @@ triggers:
 
 # SDLC Reference
 
-默认执行不从这里开始，而是从根级 `skills/flow/SKILL.md` 和各 core `skills/*/SKILL.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
+默认执行不从这里开始，而是从根级 `skills/flow/SOURCE.md` 和各 core `skills/*/SOURCE.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
 
 ## 阶段边界
 

package/{coding → zsk-archive}/harness/contracts/skill-classification.yaml

@@ -211,6 +211,17 @@ skills:
     rationale: Proves changed behavior locally but usually checks an implementation rather than producing a standalone phase artifact.
     migration: Move under quality gates for coding/demo/release flows.
 
+  check:
+    currentInstallKind: workflow-node
+    currentCategory: stage
+    skillType: capability
+    targetPrimary: gate
+    disposition: downshift-to-gate
+    facets: [quality-assessment, evidence, release]
+    stageEligible: false
+    rationale: Runs lightweight readiness preflight over local changes or explicit targets without owning review, verify, approval, commit, or release.
+    migration: Keep as an optional preflight capability/gate selected by workflow profiles or direct user requests.
+
   review:
     currentInstallKind: workflow-node
     currentCategory: stage
@@ -364,3 +375,14 @@ skills:
     stageEligible: true
     rationale: Learning feedback can become a stage in learning workflows but is usually reusable governance capability after archive/review.
     migration: Keep as learning capability with stage eligibility for explicit learning optimization workflows.
+
+  health:
+    currentInstallKind: workflow-node
+    currentCategory: stage
+    skillType: capability
+    targetPrimary: capability
+    disposition: keep-capability
+    facets: [quality-assessment, documentation-feedback]
+    stageEligible: false
+    rationale: Diagnoses skill, workflow, harness, generated-surface, and install health to reduce coupling and token waste without owning product delivery.
+    migration: Keep as an optional diagnostic capability selected by maintainers, workflows, or direct troubleshooting prompts.