create-yss-spec 3.3.1 → 3.3.3

package/template/.pi/skills/yss-ui/assets/docs/guide/llms.md

@@ -28,7 +28,7 @@ LLMs.txt 是一个专门为大语言模型设计的文档格式规范。通过
 包含所有组件的完整 API 文档、使用示例和最佳实践。**强烈推荐**作为默认配置，因为：
 - ✅ **更准确的代码生成** - AI 能看到完整的 Props、Events、Slots 定义
 - ✅ **真实示例参考** - 包含实际使用代码，避免 AI 猜测用法
-- ✅ **完整上下文** - 现代 AI 工具（Claude 200K、GPT-4 128K）完全支持这个大小
+- ✅ **完整上下文** - 现代 AI 工具的大上下文窗口可完整加载文档
 
 ### 轻量级索引：llms.txt
 
@@ -96,60 +96,6 @@ Always reference the YSS UI documentation when working with components:
 
 ---
 
-### Claude Code
-
-在 Claude Code 中，将 LLMs.txt 添加到工作区的知识库（Docs / Context Files）配置中，即可在代码补全与解释时引用其中的内容。
-
-**使用方法：**
-
-1. 打开 Claude Code 设置
-2. 找到 "Docs / Context Files" 配置
-3. 添加 `http://192.168.164.27:3200/llms-full.txt`
-
-<a href="https://code.claude.com/docs" target="_blank">详细了解 Claude Code 文档上下文配置</a>
-
----
-
-### Trae
-
-在 Trae 中，将 LLMs.txt 文件放入项目的 knowledge sources 并在设置里开启引用。
-
-**使用方法：**
-
-1. 打开 Trae 项目设置
-2. 找到 "Knowledge Sources" 配置
-3. 添加 `http://192.168.164.27:3200/llms-full.txt`
-4. 启用该知识源
-
-<a href="https://trae.ai/docs" target="_blank">详细了解 Trae 的知识源功能</a>
-
----
-
-### Qoder
-
-在 Qoder 中，可以在 `.qoder/config.yml` 中添加 LLMs.txt 作为外部知识文件，或在对话中通过 `@docs` 进行临时引用。
-
-**使用方法 1：配置文件**
-
-在项目根目录创建 `.qoder/config.yml`：
-
-```yaml
-knowledge:
-  external_docs:
-    - url: http://192.168.164.27:3200/llms-full.txt
-      name: YSS UI Documentation
-```
-
-**使用方法 2：临时引用**
-
-```
-@docs http://192.168.164.27:3200/llms-full.txt
-```
-
-<a href="https://docs.qoder.com/" target="_blank">详细了解 Qoder 配置方法</a>
-
----
-
 ### 其他 AI 工具
 
 任何支持 LLMs.txt 的 AI 工具均可使用以上路径来更好地理解 YSS UI。

package/template/AGENTS.md

@@ -30,12 +30,6 @@
 - 每仓只允许根目录一个大小写精确的 `CONTEXT.md`；禁止嵌套、`CONTEXT-MAP.md`、跨仓路径和伪锚点。
 - `project-instance` 每个工作单元批准或流转前完成 `context_reconciliation`；缺失、冲突或摘要漂移即 `blocked`。`template-source` 校验模板合同并记录带原因的 `not-applicable`。
 
-## 4. `template-source` 模板维护路由
-
-- 按“影响面 → 事实源 → 投影 / 派生 → 分级证据”维护；改 Skill 必须用 `maintaining-skills`，并按 `docs/process/harness-process-tailoring.md` 判定 L1 / L2 / L3。
-- `.agents/skills` 是共享 Skill 权威目录；其他 Agent root 下的同名 Skill 是生成投影，不得手改或与 canonical 并列维护。
-- 内循环运行 `scripts/verify-template-fast`；晋级审查运行 `scripts/verify-template-candidate`；首次冻结和最终发布前运行不可裁剪的 `scripts/verify-template`。外部 `create-yss-spec` 集成未闭合不得称可发布。
-
 ## 5. `project-instance` 产品研发路由
 
 主流程：分诊 → Plan → Spec / 功能架构 → 产品设计 → 工程契约 → Ticket → 切片 → 验证 / 发布 / 复盘。

package/template/CONTEXT.md

@@ -16,7 +16,7 @@ context_schema_version: 1
 | 术语 | 含义 | 英文标识 | 避免 / 备注 |
 |---|---|---|---|
 | Plan（战略规划） | 确认目标、业务边界、关键规则、MVP / 非目标、优先级和交接责任，为 Spec 提供已确认的战略输入。 | — | 问题探索是其中按需开展的活动；不等同于 AI-DLC 官方阶段名、交付排期或实现合同的 Context Plan。旧阶段 ID 已弃用，不提供兼容解析。 |
-| Agent | 执行特定工作流步骤的 AI 协作者。 | — | 不要与生物人审查者、数字人角色或 Ticket 状态混用。运行时实例（Cursor Agent、Claude Code、Grok Bot 等）是 Agent 的承载，不是角色本身。 |
+| Agent | 执行特定工作流步骤的 AI 协作者。 | — | 不要与生物人审查者、数字人角色或 Ticket 状态混用。运行时实例（Cursor Agent、Codex、Grok Bot 等）是 Agent 的承载，不是角色本身。 |
 | 运行时绑定 | 把数字人角色落到某个 Agent 平台的适配声明，权威清单在数字人角色注册表的 `runtimes`。 | — | 不要为每个平台复制一套职称职责。 |
 | Grok Bot | Grok 平台上的持久数字队友实例；对应 `runtime.grok`。 | — | 不是数字人角色、技能或门禁。 |
 | 数字人角色 | 叠加在生命周期编排器上的职称配置；一个运行时实例绑定一种。v1 清单以 `docs/agents/digital-human-roles.yaml` 为准。 | — | 不要称为 Ticket「标准角色」、职能 Agent 或某个平台的产品名。 |
@@ -59,8 +59,8 @@ context_schema_version: 1
 | ADR | 架构决策记录，用于沉淀难以回滚、非显而易见且存在真实取舍的技术决策。 | — | 常规实现选择不要写 ADR。 |
 | Fresh Verification | 完成前重新执行的验证证据，包括测试命令、契约校验、关键路径检查或人工审查结论。 | — | 不等同于“之前跑过”或实现者自述。 |
 | `implementation-ready` | 模板维护实现和命中影响面的快速核验已经完成，但尚未冻结正式审查候选。 | — | 是模板维护默认出口；不等同于 `ready-for-agent`、已审查或可发布。 |
-| `review-ready` | 模板维护候选已完成 candidate 核验、首次完整发布门禁和摘要冻结，可以派发独立审查。 | — | Reviewer 必须消费同一候选摘要；候选字节变化后旧审查失效。 |
-| `release-ready` | 模板维护冻结候选已经通过独立审查和最终完整 Fresh Verification。 | — | 仍不替代 `gate.release-ready` 所需的生物人发布裁决。 |
+| `review-ready` | 模板维护显式选择独立审查时的就绪状态；旧候选协议要求 candidate 核验、首次完整验证和摘要冻结。 | — | Reviewer 必须消费同一候选摘要；候选字节变化后旧审查失效。 |
+| `release-ready` | 模板维护已完成维护者自检和发布前完整 Fresh Verification；显式选择独立审查时还须闭合该审查。 | — | 仍不替代 `gate.release-ready` 所需的生物人发布裁决。 |
 | 实现验证命令 | 前端测试 / 构建优先 `pnpm`，后端校验 / 测试 / 编译优先 `./mvnw`。 | — | 不要默认 `npm`、`yarn` 或裸 `mvn`；仓库确实缺少 pnpm 或 Maven Wrapper 时记受控例外。 |
 | 脚手架架构选择 | 新建后端工程在工程基线中对 `domain-driven` 与 `layered-mvc` 的结构化选择；Agent 提供证据化推荐，用户确认后由生命周期批准并供脚手架合同消费。 | — | 不是新门禁，也不是生成器内的交互参数；缺失、未确认或摘要漂移时阻断生成。 |
 | 测试质量基线 | 项目实例明确采纳的覆盖率阈值、关键流程清单和受控例外。 | — | 模板推荐值本身不构成可执行门禁；未定义关键流程时，不得声称其 E2E 覆盖率达到 100%。 |
@@ -102,6 +102,9 @@ context_schema_version: 1
 | 模板实例分发面 | 模板源中应随 CLI 快照进入 `project-instance` 的共享生命周期、模板、用户指南和验证资产集合。 | — | 不包含模板源审查、研究、发布路线、源仓库专属 ADR 或源仓库 LLM Wiki 编译树。 |
 | 模板源治理区 | 仅供 `template-source` 使用、保存审查证据、研究记录、跨仓契约、发布路线、源仓库治理决策和源仓库 LLM Wiki 编译树的归档区域。 | — | 不随 CLI 分发；不等于产品实例的研发管理资产。`wiki-root` 为 `.template-source/wiki`。 |
 | 仓库身份清单 | 显式声明仓库身份和清单结构版本的机器可读资产。 | — | 不承载项目名称、团队规模、Tracker 或其他易变业务配置。 |
+| 聚合门禁 | 汇总适用自动检查和独立专业审查后，对当前资产与范围作一次批准或验收；权威定义见生命周期注册表。 | — | 内部检查失败仍阻断；有效批准只在相关依据、范围或授权变化时失效。 |
+| 内部检查 | 以 `check.*` 登记的自动前置核验、计算状态或独立专业审查；作为聚合门禁输入，不单独请求用户批准。 | — | 不等于省略检查或允许起草者自审。 |
+| 交付验收 | 对当前交付候选的独立审查、实际验证和回滚证据作出验收结论。 | — | 不授予实际合并、推送或发布权限；这些动作另按授权范围执行。 |
 
 ## 业务术语
 

package/template/README.md

@@ -10,12 +10,9 @@
 
 ```text
 ├── .agents/                 ← 跨 Agent 共享 skills 的权威内容
-├── .claude/                 ← Claude skills 投影与平台专属 skills
 ├── .codex/                  ← Codex skills 投影与平台专属 skills
 ├── .cursor/                 ← Cursor skills 投影
 ├── .pi/                     ← Pi skills 投影与平台专属 skills
-├── .qoder/                  ← Qoder skills 投影与平台专属 skills
-├── .trae/                   ← Trae skills 投影与平台专属 skills
 ├── AGENTS.md                ← AI 指令
 ├── CONTEXT.md               ← 领域词汇表
 ├── yss-project.yaml         ← 仓库身份清单

package/template/__yss_dotfile__.gitignore

@@ -1,3 +1,4 @@
+# >>> create-yss-spec managed rules
 # Python
 __pycache__/
 *.py[cod]
@@ -13,12 +14,12 @@ dist/
 
 # IDE
 .idea/
-.vscode/
 .DS_Store
 
 # Secrets
 .env
 .env.*
+!.env.example
 *.pem
 
 # Database
@@ -28,17 +29,9 @@ dist/
 # Logs
 *.log
 logs/
-.template-source/cache/
 
 # Coverage
 htmlcov/
 .coverage
 .pytest_cache/
-Excalidraw
-.obsidian
-.ua
-output
-docs/process/presentations/
-docs/process/yss-product-lifecycle-team-guide.md
-docs/graphify-out
-docs/.scratch/
+# <<< create-yss-spec managed rules

package/template/docs/agents/digital-human-roles.md

@@ -1,6 +1,6 @@
 # 数字人角色
 
-结构化事实源是 `docs/agents/digital-human-roles.yaml`。角色、技能、协作组和会签级别与运行时无关。Claude Code、Cursor、Codex、Grok Bot 等只通过 YAML `runtimes` 绑定。冲突时以 YAML 为准。
+结构化事实源是 `docs/agents/digital-human-roles.yaml`。角色、技能、协作组和会签级别与运行时无关。Cursor、Codex、Grok Bot 等只通过 YAML `runtimes` 绑定。冲突时以 YAML 为准。
 
 ## 何时读本文
 
@@ -14,27 +14,15 @@
 | 主控数字人 | 生命周期编排器的运行时实例 | 第八个业务职称 |
 | 职能工作单元 | Plan / Spec / Code / Review | 职称 |
 | 执行态 | Explorer / Drafter / Worker / Reviewer / Verifier | 数字人角色 |
-| 运行时绑定 | 如何在 Cursor / Claude / Grok 等落地 | 角色职责本身 |
+| 运行时绑定 | 如何在 Cursor / Codex / Grok 等落地 | 角色职责本身 |
 
 一次数字人任务包同时写明 `task_id`、`work_unit_id`、`actor_id`、数字人角色、执行态、当前 `runtime_id`，以及从角色表复制的 `core_skills` / `forbidden_skills`。可用 `taskPackageDefaults(roleId)`（`scripts/lib/digital-human-roles.mjs`）读取，禁止手写第二套技能包。`role.test-engineer` 的 core_skills 含 YSS / Alibaba 专项 skill，仅作为 `code-review` Standards 只读输入，不得写实现；finding 交实现者修复或回 实现合同编译器，审查者不得当场改代码。任务包 canonical Schema 为 `docs/process/schemas/digital-human-task-package.schema.json`，按 `contract.kind` 选择生命周期、切片实现或模板维护合同。
 
 ## 会签人
 
-`gate_policy.digital_human_review` 与 `dual_digital_human` 是「门禁 × 起草者 × 会签人」规则，不是门禁名单。主控按 `countersigners` 派会签任务。
+正式门禁的会签由 `gate_policy.digital_human_review` / `dual_digital_human` / `biological_human` 定义；内部专业审查由 `check_reviews` 定义，自动检查由 `automatic_checks` 定义。每项的起草者与会签人只读取 YAML，不在本文复制名单。
 
-| 门禁 / 工作单元 | 起草 | 会签 |
-|---|---|---|
-| `gate.prototype-reviewed` | `role.product-manager` | `role.frontend-engineer` |
-| `gate.openapi-draft-reviewed` | `role.backend-engineer` | `role.frontend-engineer` |
-| `gate.engineering-baseline-accepted` | （实现者） | `role.test-engineer` |
-| `gate.frontend-implementation-verified` | `role.frontend-engineer` | `role.test-engineer` |
-| `work-unit.code-review` | 实现者 | `role.test-engineer`（必须不同实例） |
-| `gate.spec-baseline-approved` | `role.requirements-manager` | `role.product-manager` |
-| `gate.openapi-frozen` | `role.backend-engineer` | `role.product-manager`、`role.test-engineer` |
-| `gate.user-confirmation` | 产品数字人提供建议 | 提问者或其明确指定的生物人负责人 |
-| `gate.release-ready` | — | 生物人（`role.biological-human`） |
-
-未列入表的门禁（含 `gate.design-reviewed`、`gate.architecture-reviewed`）走 `default_if_unlisted: biological-human`。
+Plan、产品设计、工程契约统一呈现适用检查后批准。`gate.delivery-accepted` 由测试角色进行交付验收，实际合并或发布仍须另有生物人授权。内部检查不独立请求用户决定；检查失败仍阻断聚合门禁。专业审查可在同一工作单元完成多个检查项，但必须保留逐项结论、资产摘要与独立执行者身份。
 
 会签写入 `docs/.scratch/<feature>/gates/<gate-id>-approval.yaml`，形状见 `docs/templates/approval-record-template.yaml`。恢复前运行 `scripts/verify-approval-record --require-approved`。错误会签只能得到 `blocked`，不能把门禁标成 `approved`。Checkpoint 里会签桶门禁为 `approved` 时必须有可读 `approval_ref`。
 
@@ -57,7 +45,7 @@
 | ID | 覆盖 | 落地方式 |
 |---|---|---|
 | `runtime.generic` | 任何能加载 `core_skills` 并接受任务包的 Agent | 通用会话 / 人设 / system prompt |
-| `runtime.skill-projection` | `yss-skill-registry.yaml` 的 `agent_runtime_roots`（claude、codex、cursor、pi、qoder、trae） | 投影技能 + subagent 任务包 |
+| `runtime.skill-projection` | `yss-skill-registry.yaml` 的 `agent_runtime_roots`（codex、cursor、pi） | 投影技能 + subagent 任务包 |
 | `runtime.grok` | Grok Bot | 持久 Bot、群聊或 1:1 交接；群超过 6 人改 1:1，不改逻辑协作组 |
 
 新增平台：先加 `runtimes` 条目，再写适配说明。不要把平台限制写进 `roles`。
@@ -71,7 +59,7 @@ Grok 专用操作见 `docs/templates/grok-bot-profile-template.md`。通用实
 | 运行时副作用审批 | 发消息、改生产、付款、删数据等工具动作 | 生物人（各平台自己的 Allow / 确认框） |
 | 生命周期会签 | `gate.*` 与独立 code review | 见 YAML `gate_policy` |
 
-会签写入 `docs/templates/approval-record-template.yaml`，带 `runtime_id`、`principal_ref` 与实例引用。起草者不得出现在会签人里。`gate.release-ready`、对外商务合同、运行时外部副作用，以及未列入会签表的 `gate.design-reviewed` / `gate.architecture-reviewed` 仍须生物人。
+会签写入 `docs/templates/approval-record-template.yaml`，带 `runtime_id`、`principal_ref` 与实例引用。起草者不得出现在会签人里。对外商务合同和运行时外部副作用仍须生物人；交付验收不授予这些权限。
 
 ## 实例化
 

package/template/docs/agents/digital-human-roles.yaml

@@ -2,9 +2,7 @@ schema_version: 1
 registry_id: yss.digital-human-roles
 status: active
 description: >-
-  数字人角色、主控、阶段协作组、技能启用/禁止与生命周期会签的单一事实源。
-  角色配置与运行时无关；Claude / Cursor / Codex / Grok 等只通过 runtimes 绑定。
-  Ticket 五态不是数字人角色。
+  数字人角色、主控、阶段协作组、技能启用/禁止与生命周期会签的单一事实源。 角色配置与运行时无关；Cursor / Codex / Grok 等只通过 runtimes 绑定。 Ticket 五态不是数字人角色。
 canonical_path: docs/agents/digital-human-roles.yaml
 runtime_policy:
   overlay_on_lifecycle: true
@@ -18,7 +16,7 @@ runtime_policy:
   biological_veto: true
   implementer_must_differ: true
   write_isolation: task-package-policy
-  dual_hat_split_when: [cross-repo-load, responsibility-conflict]
+  dual_hat_split_when: [ cross-repo-load, responsibility-conflict ]
 
 runtimes:
   - id: runtime.generic
@@ -43,9 +41,7 @@ runtimes:
     shared_workspace_is_not_security_boundary: false
     side_effect_approval: biological-human
     notes: >-
-      覆盖 docs/agents/yss-skill-registry.yaml 的 agent_runtime_roots
-      （claude / codex / cursor / pi / qoder / trae）。
-      技能仍从 .agents/skills 投影，不按职称再维护一份。
+      覆盖 docs/agents/yss-skill-registry.yaml 的 agent_runtime_roots （codex / cursor / pi）。 技能仍从 .agents/skills 投影，不按职称再维护一份。
   - id: runtime.grok
     kind: grok-bot
     instance_kind: durable-bot
@@ -58,25 +54,19 @@ runtimes:
     shared_workspace_is_not_security_boundary: true
     side_effect_approval: biological-human
     notes: >-
-      Grok Bot 适配。群聊 2–6 人；超出则改 1:1 交接，不改逻辑阶段协作组。
-      全部 Bot 共享云计算机，写范围只靠任务包。不新增 agent_runtime_roots.grok。
+      Grok Bot 适配。群聊 2–6 人；超出则改 1:1 交接，不改逻辑阶段协作组。 全部 Bot 共享云计算机，写范围只靠任务包。不新增 agent_runtime_roots.grok。
 
 orchestrator:
   id: role.lifecycle-orchestrator
   name: 主控数字人
   kind: orchestrator
   title: YSS 生命周期主控
-  default_dual_hat: [role.project-manager]
-  stages: [stage.entry-triage, stage.plan, stage.spec-architecture, stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-  core_skills: [yss-product-lifecycle, yss-implementation-contract-compiler]
-  forbidden_skills: [yss-domain, yss-ui, yss-ui-business-page-generation, yss-web-controller, yss-repository, implement]
+  default_dual_hat: [ role.project-manager ]
+  stages: [ stage.entry-triage, stage.plan, stage.spec-architecture, stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+  core_skills: [ yss-product-lifecycle, yss-implementation-contract-compiler ]
+  forbidden_skills: [ yss-domain, yss-ui, yss-ui-business-page-generation, yss-web-controller, yss-repository, implement ]
   description: >-
-    Own YSS lifecycle routing. Read yss-project.yaml and CONTEXT.md first.
-    Select the next unblocked work unit, compile a task package, and assign
-    one owner per stage. Do not implement business code. Do not approve Slice
-    contracts into ready-for-agent without the full formula. Do not announce
-    releasable. Default dual-hat: project manager until a separate instance
-    is required. Authoritative artifacts live in git.
+    Own YSS lifecycle routing. Read yss-project.yaml and CONTEXT.md first. Select the next unblocked work unit, compile a task package, and assign one owner per stage. Do not implement business code. Do not approve Slice contracts into ready-for-agent without the full formula. Do not announce releasable. Default dual-hat: project manager until a separate instance is required. Authoritative artifacts live in git.
 
 roles:
   - id: role.requirements-manager
@@ -84,177 +74,174 @@ roles:
     kind: digital-human
     contract_version: 1
     title: YSS 需求经理
-    stages: [stage.plan, stage.spec-architecture]
-    draft_artifact_ids: [artifact.plan-record, artifact.spec]
-    core_skills: [grilling, domain-modeling, yss-research, competitive-intelligence, grill-with-docs]
-    forbidden_skills: [yss-ui, yss-domain, yss-web-controller, yss-repository, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, yss-frontend-scaffold-generator, implement, tdd]
+    stages: [ stage.plan, stage.spec-architecture ]
+    draft_artifact_ids: [ artifact.plan-record, artifact.spec ]
+    core_skills: [ grilling, domain-modeling, yss-research, competitive-intelligence, grill-with-docs ]
+    forbidden_skills: [ yss-ui, yss-domain, yss-web-controller, yss-repository, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, yss-frontend-scaffold-generator, implement, tdd ]
     description: >-
-      Own Plan language, users, MVP, non-goals, success criteria, test
-      seams, and Spec prose. Propose CONTEXT.md glossary entries. Do not freeze
-      visual prototypes, OpenAPI, or code. Do not guess unconfirmed business
-      rules. Hand off to the orchestrator when the frontier is empty.
+      Own Plan language, users, MVP, non-goals, success criteria, test seams, and Spec prose. Propose CONTEXT.md glossary entries. Do not freeze visual prototypes, OpenAPI, or code. Do not guess unconfirmed business rules. Hand off to the orchestrator when the frontier is empty.
 
   - id: role.product-manager
     name: 产品经理
     kind: digital-human
     contract_version: 1
     title: YSS 产品经理
-    stages: [stage.plan, stage.spec-architecture, stage.product-design, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.product-overview, artifact.functional-architecture, artifact.interaction-spec, artifact.state-matrix, artifact.prototype-confirmation]
-    core_skills: [yss-design-system, yss-prototype-stage, prototype-review, yss-antdv-next-design, yss-research, competitive-intelligence]
-    forbidden_skills: [yss-ui, yss-domain, yss-repository, yss-web-controller, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, implement, tdd]
+    stages: [ stage.plan, stage.spec-architecture, stage.product-design, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.product-overview, artifact.functional-architecture, artifact.interaction-spec, artifact.state-matrix, artifact.prototype-confirmation ]
+    core_skills: [ yss-design-system, yss-prototype-stage, prototype-review, yss-antdv-next-design, yss-research, competitive-intelligence ]
+    forbidden_skills: [ yss-ui, yss-domain, yss-repository, yss-web-controller, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, implement, tdd ]
     description: >-
-      Own priority, product-design impact, interaction, state matrix, prototype
-      confirmation recommendation, and the commercial constraints, delivery
-      commitments, release window, and commercial non-goals for Plan and
-      release. May reject Spec scope. Do not write production code or freeze
-      OpenAPI alone. Do not independently approve external commercial contracts
-      or formal commitments; those require biological-human approval. Frontend
-      implementation uses the frontend-engineer role and yss-ui, not
-      yss-antdv-next-design. Explicit React/AntD compatibility prototypes use
-      yss-antd-design conditionally.
+      Own priority, product-design impact, interaction, state matrix, prototype confirmation recommendation, and the commercial constraints, delivery commitments, release window, and commercial non-goals for Plan and release. May reject Spec scope. Do not write production code or freeze OpenAPI alone. Do not independently approve external commercial contracts or formal commitments; those require biological-human approval. Frontend implementation uses the frontend-engineer role and yss-ui, not yss-antdv-next-design. Explicit React/AntD compatibility prototypes use yss-antd-design conditionally.
 
   - id: role.project-manager
     name: 项目经理
     kind: digital-human
     contract_version: 1
     title: YSS 项目经理
-    stages: [stage.entry-triage, stage.plan, stage.spec-architecture, stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.parent-ticket, artifact.vertical-slice-ticket]
-    core_skills: [yss-product-lifecycle, handoff, implementation-repo-onboarding, cross-repo-implementation-routing]
-    forbidden_skills: [yss-domain, yss-ui, implement, tdd, yss-web-controller]
+    stages: [ stage.entry-triage, stage.plan, stage.spec-architecture, stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.parent-ticket, artifact.vertical-slice-ticket ]
+    core_skills: [ yss-product-lifecycle, handoff, implementation-repo-onboarding, cross-repo-implementation-routing ]
+    forbidden_skills: [ yss-domain, yss-ui, implement, tdd, yss-web-controller ]
     description: >-
-      Own parent Ticket hygiene, checkpoints, handoff, risk, and implementation
-      repo registry. Do not set ready-for-agent; the orchestrator recomputes
-      that formula. Do not approve Spec or OpenAPI Freeze. Do not write business
-      code or serve as independent Reviewer. Default dual-hat on the
-      orchestrator instance until dual_hat_split_when
-      (cross-repo-load or responsibility-conflict) requires a separate instance.
+      Own parent Ticket hygiene, checkpoints, handoff, risk, and implementation repo registry. Do not set ready-for-agent; the orchestrator recomputes that formula. Do not approve Spec or OpenAPI Freeze. Do not write business code or serve as independent Reviewer. Default dual-hat on the orchestrator instance until dual_hat_split_when (cross-repo-load or responsibility-conflict) requires a separate instance.
 
   - id: role.frontend-engineer
     name: 前端工程师
     kind: digital-human
     contract_version: 1
     title: YSS 前端工程师
-    stages: [stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.frontend-implementation-plan]
-    core_skills: [yss-ui, yss-ui-business-page-generation, yss-components, yss-formily, formily-foundation, formily-linkage-effects, formily-mode-slot-detail, formily-step-flow, ytable-usage, ytree-usage, yedit-table-usage, yss-api-integration, yss-hook, theme-token-usage, page-skeleton, page-list-module, page-form-module, component-selection-imports, vue3-best-practices, tdd]
-    forbidden_skills: [yss-domain, yss-application, yss-repository, yss-mybatis, yss-web-controller, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, java-backend-commit]
+    stages: [ stage.product-design, stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.frontend-implementation-plan ]
+    core_skills: [ yss-ui, yss-ui-business-page-generation, yss-components, yss-formily, formily-foundation, formily-linkage-effects, formily-mode-slot-detail, formily-step-flow, ytable-usage, ytree-usage, yedit-table-usage, yss-api-integration, yss-hook, theme-token-usage, page-skeleton, page-list-module, page-form-module, component-selection-imports, vue3-best-practices, tdd ]
+    forbidden_skills: [ yss-domain, yss-application, yss-repository, yss-mybatis, yss-web-controller, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, java-backend-commit ]
     description: >-
-      Own Vue page modules, frontend tests, and frontend_implementation_plan.
-      Review OpenAPI Draft for client fit and prototype feasibility. Write only
-      contract-allowed frontend paths. Verify with pnpm. Do not freeze API, own
-      backend domain, or countersign your own merge.
+      Own Vue page modules, frontend tests, and frontend_implementation_plan. Review OpenAPI Draft for client fit and prototype feasibility. Write only contract-allowed frontend paths. Verify with pnpm. Do not freeze API, own backend domain, or countersign your own merge.
 
   - id: role.backend-engineer
     name: 后端工程师
     kind: digital-human
     contract_version: 1
     title: YSS 后端工程师
-    stages: [stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.openapi-draft, artifact.data-architecture, artifact.technical-design]
-    core_skills: [yss-implementation-contract-compiler, yss-technical-design, yss-tactical-design, yss-mvc-design, yss-domain, yss-application, yss-repository, yss-mybatis, yss-web-controller, yss-dto, mapstruct, lombok, alibaba-java-code-style, yss-exception, yss-validation, tdd, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator]
-    forbidden_skills: [yss-ui, yss-ui-business-page-generation, yss-formily, yss-frontend-scaffold-generator, yss-antd-design, yss-antdv-next-design, page-list-module, page-form-module]
+    stages: [ stage.system-data-engineering, stage.ticket-formalization, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.openapi-draft, artifact.data-architecture, artifact.technical-design ]
+    core_skills: [ yss-implementation-contract-compiler, yss-technical-design, yss-tactical-design, yss-mvc-design, yss-domain, yss-application, yss-repository, yss-mybatis, yss-web-controller, yss-dto, mapstruct, lombok, alibaba-java-code-style, yss-exception, yss-validation, tdd, yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator ]
+    forbidden_skills: [ yss-ui, yss-ui-business-page-generation, yss-formily, yss-frontend-scaffold-generator, yss-antd-design, yss-antdv-next-design, page-list-module, page-form-module ]
     description: >-
-      Own OpenAPI Draft, data-architecture contributions, and backend tests.
-      Write only contract-allowed backend paths. Verify with ./mvnw. Do not
-      Freeze OpenAPI, treat UI copy as requirements, or countersign your own
-      implementation.
+      Own OpenAPI Draft, data-architecture contributions, and backend tests. Write only contract-allowed backend paths. Verify with ./mvnw. Do not Freeze OpenAPI, treat UI copy as requirements, or countersign your own implementation.
 
   - id: role.test-engineer
     name: 测试工程师
     kind: digital-human
     contract_version: 1
     title: YSS 测试工程师
-    stages: [stage.spec-architecture, stage.vertical-slice-implementation, stage.verification-release-retrospective]
-    draft_artifact_ids: [artifact.frontend-implementation-verification]
-    owned_evidence_ids: [evidence.fresh-verification, evidence.frontend-implementation-verification]
-    core_skills: [tdd, diagnosing-bugs, code-review, alibaba-java-code-style, yss-ui, yss-design-system, yss-ui-business-page-generation, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok]
-    forbidden_skills: [yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, yss-frontend-scaffold-generator, implement, to-spec]
+    stages: [ stage.spec-architecture, stage.vertical-slice-implementation, stage.verification-release-retrospective ]
+    draft_artifact_ids: [ artifact.frontend-implementation-verification ]
+    owned_evidence_ids: [ evidence.fresh-verification, evidence.frontend-implementation-verification ]
+    core_skills: [ tdd, diagnosing-bugs, code-review, alibaba-java-code-style, yss-ui, yss-design-system, yss-ui-business-page-generation, yss-domain, yss-application, yss-repository, yss-web-controller, yss-dto, mapstruct, lombok ]
+    forbidden_skills: [ yss-ddd-scaffold-generator, yss-layered-mvc-scaffold-generator, yss-frontend-scaffold-generator, implement, to-spec ]
     description: >-
-      Own test code, defect records, fresh verification, and frontend
-      implementation verification evidence. Review every implementation slice
-      through the unique code-review skill, loading YSS and Alibaba specialist
-      skills as read-only Standards sources. Recommend release readiness; do
-      not close gate.release-ready. Do not change product scope or write
-      feature implementation. Must be a different instance from the implementer.
+      Own test code, defect records, fresh verification, and frontend implementation verification evidence. Review every implementation slice through the unique code-review skill, loading YSS and Alibaba specialist skills as read-only Standards sources. Recommend release readiness; do not close gate.delivery-accepted. Do not change product scope or write feature implementation. Must be a different instance from the implementer.
 
 stage_groups:
   - id: group.plan
     name: Plan
     stage: stage.plan
-    members: [role.lifecycle-orchestrator, role.requirements-manager, role.product-manager]
+    members: [ role.lifecycle-orchestrator, role.requirements-manager, role.product-manager ]
   - id: group.spec
     name: Spec
     stage: stage.spec-architecture
-    members: [role.lifecycle-orchestrator, role.requirements-manager, role.product-manager, role.test-engineer]
+    members: [ role.lifecycle-orchestrator, role.requirements-manager, role.product-manager, role.test-engineer ]
   - id: group.product-design
     name: 产品设计
     stage: stage.product-design
-    members: [role.lifecycle-orchestrator, role.product-manager, role.requirements-manager, role.frontend-engineer]
+    members: [ role.lifecycle-orchestrator, role.product-manager, role.requirements-manager, role.frontend-engineer ]
   - id: group.contract
     name: 契约
     stage: stage.system-data-engineering
-    members: [role.lifecycle-orchestrator, role.backend-engineer, role.frontend-engineer, role.test-engineer, role.product-manager]
+    members: [ role.lifecycle-orchestrator, role.backend-engineer, role.frontend-engineer, role.test-engineer, role.product-manager ]
   - id: group.tickets
     name: Ticket 正式化
     stage: stage.ticket-formalization
-    members: [role.lifecycle-orchestrator, role.project-manager, role.frontend-engineer, role.backend-engineer, role.test-engineer]
+    members: [ role.lifecycle-orchestrator, role.project-manager, role.frontend-engineer, role.backend-engineer, role.test-engineer ]
   - id: group.implementation
     name: 实现
     stage: stage.vertical-slice-implementation
-    members: [role.lifecycle-orchestrator, role.frontend-engineer, role.backend-engineer, role.test-engineer]
+    members: [ role.lifecycle-orchestrator, role.frontend-engineer, role.backend-engineer, role.test-engineer ]
   - id: group.release
     name: 发布
     stage: stage.verification-release-retrospective
-    members: [role.lifecycle-orchestrator, role.project-manager, role.test-engineer, role.product-manager]
+    members: [ role.lifecycle-orchestrator, role.project-manager, role.test-engineer, role.product-manager ]
 
 gate_policy:
   default_if_unlisted: biological-human
-  unlisted_kept_biological:
-    - gate.design-reviewed
-    - gate.architecture-reviewed
-  evidence_only:
-    - gate.frontend-delivery-inputs-verified
-    - gate.repository-identity-valid
-    - gate.prototype-verified
+  evidence_only: []
   orchestrator:
-    - gate.implementation-repositories-ready
     - gate.slice-contract-approved
-    - gate.slice-ready-for-agent
   digital_human_review:
-    - gate: gate.prototype-reviewed
-      drafter: role.product-manager
-      countersigners: [role.frontend-engineer]
-    - gate: gate.openapi-draft-reviewed
-      drafter: role.backend-engineer
-      countersigners: [role.frontend-engineer]
-    - gate: gate.engineering-baseline-accepted
-      countersigners: [role.test-engineer]
-    - gate: gate.frontend-implementation-verified
-      drafter: role.frontend-engineer
-      countersigners: [role.test-engineer]
+    - gate: gate.delivery-accepted
+      countersigners:
+        - role.test-engineer
   digital_human_review_work_units:
     - work_unit: work-unit.code-review
-      countersigners: [role.test-engineer]
+      countersigners:
+        - role.test-engineer
       implementer_must_differ: true
   dual_digital_human:
-    - gate: gate.spec-baseline-approved
-      drafter: role.requirements-manager
-      countersigners: [role.product-manager]
-    - gate: gate.domain-strategy-approved
+    - gate: gate.plan-approved
       drafter: role.requirements-manager
-      countersigners: [role.product-manager]
-    - gate: gate.stage-decision-package-approved
+      countersigners:
+        - role.product-manager
+    - gate: gate.spec-baseline-approved
       drafter: role.requirements-manager
-      countersigners: [role.product-manager]
-    - gate: gate.openapi-frozen
+      countersigners:
+        - role.product-manager
+    - gate: gate.engineering-contract-approved
       drafter: role.backend-engineer
-      countersigners: [role.product-manager, role.test-engineer]
+      countersigners:
+        - role.product-manager
+        - role.test-engineer
   product_digital_human_with_biological_veto: []
   biological_human:
-    - gate.user-confirmation
-    - gate.release-ready
+    - gate.product-design-approved
+  automatic_checks:
+    - check.repository-identity-valid
+    - check.frontend-delivery-inputs-verified
+    - check.prototype-verified
+    - check.implementation-repositories-ready
+    - check.slice-ready-for-agent
+    - check.openapi-frozen
+  check_reviews:
+    - gate: check.domain-strategy-approved
+      drafter: role.requirements-manager
+      countersigners:
+        - role.product-manager
+    - gate: check.stage-decision-package-approved
+      drafter: role.requirements-manager
+      countersigners:
+        - role.product-manager
+    - gate: check.prototype-reviewed
+      drafter: role.product-manager
+      countersigners:
+        - role.frontend-engineer
+    - gate: check.openapi-draft-reviewed
+      drafter: role.backend-engineer
+      countersigners:
+        - role.frontend-engineer
+    - gate: check.design-reviewed
+      countersigners:
+        - role.backend-engineer
+        - role.test-engineer
+    - gate: check.architecture-reviewed
+      countersigners:
+        - role.backend-engineer
+        - role.test-engineer
+    - gate: check.engineering-baseline-accepted
+      countersigners:
+        - role.test-engineer
+    - gate: check.frontend-implementation-verified
+      drafter: role.frontend-engineer
+      countersigners:
+        - role.test-engineer
   runtime_side_effect_approval: biological-human
   commercial_contract: biological-human
 
@@ -263,29 +250,24 @@ user_decision_policy:
   schema_version: 1
   default_responder: requester
   delegate_requires_requester_evidence: true
-  source_kinds: [platform-message, session-export, user-confirmation-file]
+  source_kinds: [ platform-message, session-export, user-confirmation-file ]
   gates:
-    - gate.domain-strategy-approved
-    - gate.stage-decision-package-approved
+    - gate.plan-approved
     - gate.spec-baseline-approved
-    - gate.user-confirmation
-    - gate.openapi-frozen
-    - gate.design-reviewed
-    - gate.architecture-reviewed
-    - gate.release-ready
+    - gate.product-design-approved
+    - gate.engineering-contract-approved
   work_units:
-    work-unit.plan-requirements: plan-conclusion
     work-unit.service-project-initialization: scaffold-choice
     work-unit.implementation-repository-preparation: scaffold-choice
     work-unit.slice-implementation: implementation-scope
-    work-unit.release-and-retrospective: gate.release-ready
   work_unit_gates:
-    work-unit.domain-strategy-design: [gate.domain-strategy-approved]
-    work-unit.stage-decision: [gate.stage-decision-package-approved]
-    work-unit.spec-synthesis: [gate.spec-baseline-approved]
-    work-unit.prototype-design: [gate.user-confirmation]
-    work-unit.technical-analysis: [gate.design-reviewed, gate.openapi-frozen, gate.architecture-reviewed]
-  conditional_decisions: [scaffold-choice, external-input, new-authorization, risk-acceptance]
+    work-unit.spec-synthesis:
+      - gate.spec-baseline-approved
+    work-unit.prototype-design:
+      - gate.product-design-approved
+    work-unit.technical-analysis:
+      - gate.engineering-contract-approved
+  conditional_decisions: [ scaffold-choice, external-input, new-authorization, risk-acceptance ]
   waiting_allows: independent-work-only
   expiry: basis-change-or-revocation-only
   record_schema: docs/process/schemas/user-decision.schema.json

package/template/docs/agents/yss-skill-registry.yaml

@@ -214,12 +214,9 @@ invocation_contract:
       exclusion_conditions: [prototype-profile:H1, component-basis:not-antdv-next, production-frontend-implementation]
       primary_output: versioned-antdv-next-facts
 agent_runtime_roots:
-  claude: .claude/skills
   codex: .codex/skills
   cursor: .cursor/skills
   pi: .pi/skills
-  qoder: .qoder/skills
-  trae: .trae/skills
 skills:
   - id: alibaba-java-code-style
     layer: specialist