@captain_z/zsk-skills 1.8.8 → 1.8.9

package/README.md

@@ -9,7 +9,7 @@ ZNorth Standard Kit 的可安装 skill 内容包。安装面现在只保留从
 | 检查项                                                                                   | 结果    | 说明                                                  |
 | ---------------------------------------------------------------------------------------- | ------- | ----------------------------------------------------- |
 | frontmatter 完整（`name` / `description` / `category` / `domain` / `tier` / `triggers`） | ✓ 24/24 | core 由 root `skills/` 生成 |
-| `name` 使用裸 slug，扁平且不含连字符                                                       | ✓ 24/24 | LLM 原生 skill 入口保持简洁；CLI 选择层使用 `zsk:<slug>` |
+| `name` 使用 `zsk-<slug>` 公共命名空间，目录同名且只含小写/数字/连字符                         | ✓ 24/24 | 避免和其它 skill 仓库裸名冲突；CLI 选择层继续使用 `zsk:<slug>` |
 | `description` 简洁表达职责和使用时机                                                       | ✓ 24/24 | 面向索引阅读；triggers 留给机器使用 |
 | `category` / `domain` / `tier` 枚举值合法                                                | ✓ 24/24 | stage/utility · core |
 | `triggers` 数组非空                                                                      | ✓ 24/24 | 至少含裸 slug |
@@ -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,10 +85,10 @@ 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 |
+| 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@zsk` | 使用 `/zsk:<slug>` 命令面 |
-| GitHub skills 管理器安装 | `npx skills add codeshareman/zsk` | 从仓库根 `skills/` 安装；不要加 `@` |
+| GitHub skills 管理器安装 | `npx skills add codeshareman/zsk` | 从仓库安装 `zsk-<slug>` 公共命名空间；不要加 `@` |
 | 准备项目资源 | `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` |
 | 不确定该用哪个阶段 skill | "用 `zsk:dispatch` 调度" | 让 OMX 围绕 ZSK skills 分配 subagents |
@@ -100,9 +100,10 @@ Direct review 只需要明确 review target（代码 diff、本地路径、stage
 - `~/.claude/skills/zsk-<slug>/SKILL.md` — Claude Code / flat target
 - `~/.codex/skills/zsk-<slug>/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/zsk-<slug>/SKILL.md` — `npx skills` / Claude plugin marketplace repository target
+- `@captain_z/zsk-skills/zsk-<slug>/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` + `/plugin install zsk@zsk`；根级 `skills/.curated/` 同时兼容 `npx skills add codeshareman/zsk`。
 
 ## 和项目知识工作区的关系
 
@@ -126,10 +127,10 @@ Skills 负责更需要判断的部分：理解已同步的 SRS、PRD、API 契
 | 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` |
@@ -139,98 +140,98 @@ Skills 负责更需要判断的部分：理解已同步的 SRS、PRD、API 契
 
 ## Skill 清单（core skills）
 
-> 内容由 `tools/catalog.ts` 从 `packages/skills/*/SKILL.md` frontmatter 生成。重生成：`pnpm catalog`。
+> 内容由 `tools/catalog.ts` 从 `packages/skills/zsk-*/SKILL.md` frontmatter 生成。重生成：`pnpm catalog`。
 > 默认 profile bundles 只安装 entry 和保留的一等 stage；capability / gate / mode 由 `zskplan` / `zsk` 内部调度或通过 custom/legacy 明确安装。Legacy aliases 仍保留 24 个 skill 以兼容旧安装。
 
 ### Entry Skills (2)
 
 用户默认只需要理解的入口。
 
-- **`zskplan`** · type: workflow · keep-entry
+- **`zsk-zskplan`** · type: workflow · keep-entry
   Use as the ZSK-aware RalphPlan-style planning entrypoint that clarifies vague intake, then freezes scope, module decomposition, skill route, expert lanes, Playwright/evidence paths, and stop conditions under .zsk.
 
-- **`zsk`** · type: workflow · keep-entry
+- **`zsk-zsk`** · type: workflow · keep-entry
   Use as the ZSK-aware Ralph-style execution loop that follows ZSK plans, dispatches expert lanes, verifies, fixes, and writes only .zsk outputs.
 
 ### Stage Skills (11)
 
 有独立产物边界、质量门禁和下游消费关系的一等阶段。
 
-- **`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)
 
 可被多个阶段复用的内部能力；默认由入口或阶段调度。
 
-- **`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)
 
 阶段内部的质量检查点或发布检查点。
 
-- **`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.
 
 ### 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.9",
   "description": "ZNorth Standard Kit — core harness-first skill content package",
   "license": "MIT",
   "files": [

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/{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-coding}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: coding
+name: zsk-coding
 description: For approved tasks, implements small scoped diffs with tests,
   evidence, and blocker reporting.
 kind: workflow-node

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

@@ -1,5 +1,5 @@
 ---
-name: commit
+name: zsk-commit
 description: After smoke and review pass, prepares a scoped commit with intent,
   evidence, and clean staging.
 kind: workflow-node

package/{commit → zsk-commit}/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/{defect → zsk-defect}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: defect
+name: zsk-defect
 description: After formal QA reports findings, normalizes defects with repro,
   evidence, FR/AC links, and fix routing.
 kind: workflow-node

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

@@ -1,5 +1,5 @@
 ---
-name: demo
+name: zsk-demo
 description: Before formal testing, runs planned demos and captures evidence
   without making acceptance claims.
 kind: workflow-node

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

@@ -1,5 +1,5 @@
 ---
-name: deploy
+name: zsk-deploy
 description: After review, deploys to non-production or demo targets with
   version, smoke evidence, and rollback owner.
 kind: workflow-node

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

@@ -1,5 +1,5 @@
 ---
-name: design
+name: zsk-design
 description: After spec freeze, maps behavior to interfaces, data flow, rollout
   plan, risks, and implementation surfaces.
 kind: workflow-node

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

@@ -1,5 +1,5 @@
 ---
-name: dispatch
+name: zsk-dispatch
 description: At task intake, asks OMX to assign subagents to the right zsk skill
   from request, state, evidence, and blockers.
 kind: workflow

package/{acceptance → zsk-dispatch}/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/{fix → zsk-fix}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: fix
+name: zsk-fix
 description: For persisted issues, diagnoses root cause, applies the smallest
   scoped correction, adds a regression guard, updates the issue, and hands off
   verification.

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

@@ -0,0 +1,49 @@
+---
+name: zsk:sdlc
+description: SDLC reference overview — stage order, delivery gates, evidence expectations, and when to use core skills versus harness rules.
+category: domain-index
+domain: sdlc
+tier: optional
+related:
+  - ./agent-orchestration.md
+  - ./quality.md
+  - ./system.md
+triggers:
+  - "sdlc reference"
+  - "delivery workflow"
+  - "stage gates"
+  - "demo verify acceptance"
+---
+
+# SDLC Reference
+
+默认执行不从这里开始，而是从根级 `skills/flow/SOURCE.md` 和各 core `skills/*/SOURCE.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
+
+## 阶段边界
+
+| 阶段 | 回答的问题 | 默认 skill |
+| --- | --- | --- |
+| Proposal | 为什么做、边界在哪里 | `zsk:proposal` |
+| Spec | 做什么，如何验收 | `zsk:spec` |
+| Design | 怎么落地、风险和回滚 | `zsk:design` |
+| Task | 任务如何拆、依赖是什么 | `zsk:task` |
+| Coding | 如何小步实现 | `zsk:coding` |
+| Smoke | 开发者如何证明改动可用 | `zsk:smoke` |
+| Review | 代码是否该被挡下 | `zsk:review` |
+| Demo | 提测前能否演示主链路 | `zsk:demo` |
+| Defect | QA 正式问题如何回流 | `zsk:defect` |
+| Ready | 修复是否可交给独立验证 | `zsk:ready` |
+| Verify | 是否满足 spec/AC/NFR | `zsk:verify` |
+| Acceptance | 业务是否接受 | `zsk:acceptance` |
+| Archive | 决策和经验留下什么 | `zsk:archive` |
+
+## 硬约束
+
+- Review、Demo、Formal Testing、Verify、Acceptance 不能合并。它们回答的问题不同，证据也不同。
+- 没有证据不能说 done、pass、ready。
+- 变更范围偏离 spec/design/task 时先记录 issue 或更新契约，不要直接改实现。
+- 可复用的流程缺口进入 harness learning proposal，不直接改标准。
+
+## 精简原则
+
+细节写进 core `SKILL.md` 或 `harness/constraints`。这里不再维护 proposal/spec/design/review 等每阶段一份参考文档，避免同一门禁写两遍。

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

@@ -1,5 +1,5 @@
 ---
-name: flow
+name: zsk-flow
 description: Starts or resumes delivery by reading state, resources, and
   blockers, then selecting the next legal stage.
 kind: workflow

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

@@ -0,0 +1,49 @@
+---
+name: zsk:sdlc
+description: SDLC reference overview — stage order, delivery gates, evidence expectations, and when to use core skills versus harness rules.
+category: domain-index
+domain: sdlc
+tier: optional
+related:
+  - ./agent-orchestration.md
+  - ./quality.md
+  - ./system.md
+triggers:
+  - "sdlc reference"
+  - "delivery workflow"
+  - "stage gates"
+  - "demo verify acceptance"
+---
+
+# SDLC Reference
+
+默认执行不从这里开始，而是从根级 `skills/flow/SOURCE.md` 和各 core `skills/*/SOURCE.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
+
+## 阶段边界
+
+| 阶段 | 回答的问题 | 默认 skill |
+| --- | --- | --- |
+| Proposal | 为什么做、边界在哪里 | `zsk:proposal` |
+| Spec | 做什么，如何验收 | `zsk:spec` |
+| Design | 怎么落地、风险和回滚 | `zsk:design` |
+| Task | 任务如何拆、依赖是什么 | `zsk:task` |
+| Coding | 如何小步实现 | `zsk:coding` |
+| Smoke | 开发者如何证明改动可用 | `zsk:smoke` |
+| Review | 代码是否该被挡下 | `zsk:review` |
+| Demo | 提测前能否演示主链路 | `zsk:demo` |
+| Defect | QA 正式问题如何回流 | `zsk:defect` |
+| Ready | 修复是否可交给独立验证 | `zsk:ready` |
+| Verify | 是否满足 spec/AC/NFR | `zsk:verify` |
+| Acceptance | 业务是否接受 | `zsk:acceptance` |
+| Archive | 决策和经验留下什么 | `zsk:archive` |
+
+## 硬约束
+
+- Review、Demo、Formal Testing、Verify、Acceptance 不能合并。它们回答的问题不同，证据也不同。
+- 没有证据不能说 done、pass、ready。
+- 变更范围偏离 spec/design/task 时先记录 issue 或更新契约，不要直接改实现。
+- 可复用的流程缺口进入 harness learning proposal，不直接改标准。
+
+## 精简原则
+
+细节写进 core `SKILL.md` 或 `harness/constraints`。这里不再维护 proposal/spec/design/review 等每阶段一份参考文档，避免同一门禁写两遍。

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

@@ -1,5 +1,5 @@
 ---
-name: issue
+name: zsk-issue
 description: Tracks defects, blockers, questions, and risks with taxonomy,
   severity, owner, reproduction, and evidence.
 kind: utility

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

@@ -0,0 +1,49 @@
+---
+name: zsk:sdlc
+description: SDLC reference overview — stage order, delivery gates, evidence expectations, and when to use core skills versus harness rules.
+category: domain-index
+domain: sdlc
+tier: optional
+related:
+  - ./agent-orchestration.md
+  - ./quality.md
+  - ./system.md
+triggers:
+  - "sdlc reference"
+  - "delivery workflow"
+  - "stage gates"
+  - "demo verify acceptance"
+---
+
+# SDLC Reference
+
+默认执行不从这里开始，而是从根级 `skills/flow/SOURCE.md` 和各 core `skills/*/SOURCE.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
+
+## 阶段边界
+
+| 阶段 | 回答的问题 | 默认 skill |
+| --- | --- | --- |
+| Proposal | 为什么做、边界在哪里 | `zsk:proposal` |
+| Spec | 做什么，如何验收 | `zsk:spec` |
+| Design | 怎么落地、风险和回滚 | `zsk:design` |
+| Task | 任务如何拆、依赖是什么 | `zsk:task` |
+| Coding | 如何小步实现 | `zsk:coding` |
+| Smoke | 开发者如何证明改动可用 | `zsk:smoke` |
+| Review | 代码是否该被挡下 | `zsk:review` |
+| Demo | 提测前能否演示主链路 | `zsk:demo` |
+| Defect | QA 正式问题如何回流 | `zsk:defect` |
+| Ready | 修复是否可交给独立验证 | `zsk:ready` |
+| Verify | 是否满足 spec/AC/NFR | `zsk:verify` |
+| Acceptance | 业务是否接受 | `zsk:acceptance` |
+| Archive | 决策和经验留下什么 | `zsk:archive` |
+
+## 硬约束
+
+- Review、Demo、Formal Testing、Verify、Acceptance 不能合并。它们回答的问题不同，证据也不同。
+- 没有证据不能说 done、pass、ready。
+- 变更范围偏离 spec/design/task 时先记录 issue 或更新契约，不要直接改实现。
+- 可复用的流程缺口进入 harness learning proposal，不直接改标准。
+
+## 精简原则
+
+细节写进 core `SKILL.md` 或 `harness/constraints`。这里不再维护 proposal/spec/design/review 等每阶段一份参考文档，避免同一门禁写两遍。

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

@@ -1,5 +1,5 @@
 ---
-name: learn
+name: zsk-learn
 description: Use after repeated friction or supplied public skill/harness
   references to learn, compare, record gaps, and prepare one reviewed ZSK
   optimization batch.

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

@@ -1,5 +1,5 @@
 ---
-name: prepare
+name: zsk-prepare
 description: After project init, collects resource origins, snapshots evidence,
   and updates config/manifests before proposal/spec.
 kind: workflow-node

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

@@ -0,0 +1,49 @@
+---
+name: zsk:sdlc
+description: SDLC reference overview — stage order, delivery gates, evidence expectations, and when to use core skills versus harness rules.
+category: domain-index
+domain: sdlc
+tier: optional
+related:
+  - ./agent-orchestration.md
+  - ./quality.md
+  - ./system.md
+triggers:
+  - "sdlc reference"
+  - "delivery workflow"
+  - "stage gates"
+  - "demo verify acceptance"
+---
+
+# SDLC Reference
+
+默认执行不从这里开始，而是从根级 `skills/flow/SOURCE.md` 和各 core `skills/*/SOURCE.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
+
+## 阶段边界
+
+| 阶段 | 回答的问题 | 默认 skill |
+| --- | --- | --- |
+| Proposal | 为什么做、边界在哪里 | `zsk:proposal` |
+| Spec | 做什么，如何验收 | `zsk:spec` |
+| Design | 怎么落地、风险和回滚 | `zsk:design` |
+| Task | 任务如何拆、依赖是什么 | `zsk:task` |
+| Coding | 如何小步实现 | `zsk:coding` |
+| Smoke | 开发者如何证明改动可用 | `zsk:smoke` |
+| Review | 代码是否该被挡下 | `zsk:review` |
+| Demo | 提测前能否演示主链路 | `zsk:demo` |
+| Defect | QA 正式问题如何回流 | `zsk:defect` |
+| Ready | 修复是否可交给独立验证 | `zsk:ready` |
+| Verify | 是否满足 spec/AC/NFR | `zsk:verify` |
+| Acceptance | 业务是否接受 | `zsk:acceptance` |
+| Archive | 决策和经验留下什么 | `zsk:archive` |
+
+## 硬约束
+
+- Review、Demo、Formal Testing、Verify、Acceptance 不能合并。它们回答的问题不同，证据也不同。
+- 没有证据不能说 done、pass、ready。
+- 变更范围偏离 spec/design/task 时先记录 issue 或更新契约，不要直接改实现。
+- 可复用的流程缺口进入 harness learning proposal，不直接改标准。
+
+## 精简原则
+
+细节写进 core `SKILL.md` 或 `harness/constraints`。这里不再维护 proposal/spec/design/review 等每阶段一份参考文档，避免同一门禁写两遍。

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

@@ -1,5 +1,5 @@
 ---
-name: preproposal
+name: zsk-preproposal
 description: Before proposal, turns a one-sentence or vague intake brief into a
   clear, reviewed product, roadmap, UX, and readiness raw resource pack.
 kind: workflow-node

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

@@ -0,0 +1,49 @@
+---
+name: zsk:sdlc
+description: SDLC reference overview — stage order, delivery gates, evidence expectations, and when to use core skills versus harness rules.
+category: domain-index
+domain: sdlc
+tier: optional
+related:
+  - ./agent-orchestration.md
+  - ./quality.md
+  - ./system.md
+triggers:
+  - "sdlc reference"
+  - "delivery workflow"
+  - "stage gates"
+  - "demo verify acceptance"
+---
+
+# SDLC Reference
+
+默认执行不从这里开始，而是从根级 `skills/flow/SOURCE.md` 和各 core `skills/*/SOURCE.md` 开始。本文件只回答一件事：zsk 的交付阶段如何分工。
+
+## 阶段边界
+
+| 阶段 | 回答的问题 | 默认 skill |
+| --- | --- | --- |
+| Proposal | 为什么做、边界在哪里 | `zsk:proposal` |
+| Spec | 做什么，如何验收 | `zsk:spec` |
+| Design | 怎么落地、风险和回滚 | `zsk:design` |
+| Task | 任务如何拆、依赖是什么 | `zsk:task` |
+| Coding | 如何小步实现 | `zsk:coding` |
+| Smoke | 开发者如何证明改动可用 | `zsk:smoke` |
+| Review | 代码是否该被挡下 | `zsk:review` |
+| Demo | 提测前能否演示主链路 | `zsk:demo` |
+| Defect | QA 正式问题如何回流 | `zsk:defect` |
+| Ready | 修复是否可交给独立验证 | `zsk:ready` |
+| Verify | 是否满足 spec/AC/NFR | `zsk:verify` |
+| Acceptance | 业务是否接受 | `zsk:acceptance` |
+| Archive | 决策和经验留下什么 | `zsk:archive` |
+
+## 硬约束
+
+- Review、Demo、Formal Testing、Verify、Acceptance 不能合并。它们回答的问题不同，证据也不同。
+- 没有证据不能说 done、pass、ready。
+- 变更范围偏离 spec/design/task 时先记录 issue 或更新契约，不要直接改实现。
+- 可复用的流程缺口进入 harness learning proposal，不直接改标准。
+
+## 精简原则
+
+细节写进 core `SKILL.md` 或 `harness/constraints`。这里不再维护 proposal/spec/design/review 等每阶段一份参考文档，避免同一门禁写两遍。

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

@@ -1,5 +1,5 @@
 ---
-name: proposal
+name: zsk-proposal
 description: Before spec, frames the problem, scope, non-goals, success
   criteria, stakeholders, risks, and resource gaps.
 kind: workflow-node