create-yss-spec 2.2.2 → 2.2.4

package/template/.codex/skills/yss-product-lifecycle/references/orchestration-contract.yaml

@@ -100,6 +100,71 @@ workflow_execution_result:
   workflow_reference:
     required: [source, skill, invocation_mode]
     allowed_sources: [yss-product-lifecycle, mattpocock/skills]
+  next_route:
+    validator: scripts/lib/lifecycle-transition.mjs
+    function: validateNextRoute
+    implementation_predecessor: work-unit.ticket-decomposition
+    null_allowed_when: [blocked, needs-human, failed, terminal_completed]
+  work_unit_requirements:
+    work-unit.ticket-decomposition:
+      completed_requires: [vertical_slice_ticket_ref, ticket_decomposition_result_ref]
+    work-unit.slice-implementation:
+      required: [predecessor_work_unit, ticket_decomposition_result_ref, ticket_decomposition_result_status, vertical_slice_ticket_ref, vertical_slice_ticket_role, vertical_slice_ticket_kind, slice_contract_ticket_ref, slice_contract_status]
+      boolean_required: [ready_for_agent, slice_contract_persisted, slice_contract_current_version]
+      validator: scripts/lib/lifecycle-transition.mjs
+      function: validateImplementationEntry
+
+task_package:
+  schema_version: 1
+  applies_to: all-formal-digital-human-dispatches
+  schema_ref: docs/process/schemas/digital-human-task-package.schema.json
+  compatibility_schema_ref: docs/process/schemas/subagent-task-package.schema.json
+  validator: scripts/verify-digital-human-task-package
+  compatibility_validator: scripts/verify-subagent-task-package
+  persistence_layout: docs/.scratch/<feature>/task-packages/<task-id>.yaml
+  required: [schema_version, task_id, work_unit_id, actor_id, role_id, runtime_id, execution_state, workflow_status, skill_source, contract, inputs, objective, allowed_write_paths, forbidden_actions, expected_outputs, expected_evidence_files, verification_commands, verification_results, downstream_consumers, convergence]
+  execution_states: [Explorer, Drafter, Worker, Reviewer, Verifier]
+  workflow_statuses: [not-started, active, paused, resolved, failed]
+  skill_source:
+    registry_ref: docs/agents/digital-human-roles.yaml
+    defaults: taskPackageDefaults(role_id)
+    copy_required: [core_skills, forbidden_skills]
+  contract:
+    kinds: [lifecycle-work-unit, slice-implementation, template-maintenance]
+    required: [kind, contract_id, contract_version, status, contract_ref]
+    status_at_dispatch: issued
+    status_after_change: [stale, blocked]
+    lifecycle-work-unit:
+      required: [lifecycle_ref]
+      forbidden: [slice_contract_ref, maintenance_ref]
+      template_source_work_unit: forbidden
+    slice-implementation:
+      required: [slice_contract_ref]
+      must_match_current_slice_contract: true
+      version_mismatch: blocked
+      stage: stage.vertical-slice-implementation
+      parent_work_unit: work-unit.slice-implementation
+      work_unit_must_be_declared_in_slice_contract: true
+    template-maintenance:
+      required: [maintenance_ref]
+      forbidden: [slice_contract_ref, lifecycle_ref]
+  dispatch:
+    owner: role.lifecycle-orchestrator
+    mode: orchestrator-one-to-one
+    per_feature_instances: forbidden
+  write_isolation:
+    policy: task-package-policy
+    changed_files_must_be_within_allowed_paths: true
+    shared_workspace_is_not_security_boundary: true
+  downstream:
+    formal_channel: [task_package_ref, contract_ref, evidence_refs, workflow_execution_result]
+    direct_chat_is_not_formal_evidence: true
+  stale:
+    owner: yss-product-lifecycle
+    on_contract_change: [mark_downstream_stale, remove_ready-for-agent, reroute]
+  compatibility:
+    legacy_results: read-only-normalize
+    schema_version: 1
 
 # Matt user-invoked skills remain explicit user entry points. Lifecycle work units
 # may prepare, validate and accept their results, but cannot invoke them or create
@@ -146,6 +211,22 @@ work_unit_routes:
     skills: [grilling, domain-modeling]
     applies_when: requirements_or_domain_boundary_unclear
     not_applicable_reason: requirements_already_confirmed
+  work-unit.domain-strategy-design:
+    native: {source: yss-product-lifecycle, skill: yss-stage-decision, invocation_mode: model-invoked}
+    primary_skill: yss-stage-decision
+    supporting_skills: [domain-modeling, research, grilling]
+    skills: [yss-stage-decision, domain-modeling, research, grilling]
+    human_gate: domain-strategy-approved
+    applies_when: domain_boundary_or_language_or_core_rule_impact
+    not_applicable_reason: no_domain_strategy_impact
+  work-unit.stage-decision:
+    native: {source: yss-product-lifecycle, skill: yss-stage-decision, invocation_mode: model-invoked}
+    primary_skill: yss-stage-decision
+    supporting_skills: [domain-modeling]
+    skills: [yss-stage-decision, domain-modeling]
+    human_gate: stage-decision-package-approved
+    applies_when: discovery_to_spec_requires_stable_decision_package
+    not_applicable_reason: existing_approved_stage_decision_current
   work-unit.spec-synthesis:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-product-lifecycle
@@ -166,8 +247,17 @@ work_unit_routes:
   work-unit.technical-analysis:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-router
-    supporting_skills: [yss-openapi-governance, yss-openapi-draft-review, codebase-design, implementation-repo-onboarding]
-    skills: [yss-openapi-governance, yss-openapi-draft-review, codebase-design, implementation-repo-onboarding, yss-router]
+    supporting_skills: [yss-openapi-governance, yss-openapi-draft-review, codebase-design, implementation-repo-onboarding, yss-tactical-design]
+    skills: [yss-openapi-governance, yss-openapi-draft-review, codebase-design, implementation-repo-onboarding, yss-tactical-design, yss-router]
+    tactical_ddd:
+      applies_when: [aggregate-impact, state-machine-impact, invariant-impact, consistency-impact, domain-event-impact, gateway-boundary-impact, persistence-mapping-impact]
+      not_applicable_reason: no_tactical_ddd_impact
+      default_artifact: system-overview-design.tactical-ddd-check
+      standalone_artifact: artifact.tactical-design
+      review_evidence: evidence.tactical-design-review
+      statuses: [draft, ready-for-human, approved, blocked, stale, drift, new_impacts, not-applicable]
+      approved_by: yss-product-lifecycle
+      forbidden: [self-approval, ready-for-agent, production-code-generation]
     human_gate: openapi-freeze_if_api_impact
     applies_when: technical_or_contract_impact
     not_applicable_reason: no_technical_or_contract_impact
@@ -179,6 +269,7 @@ work_unit_routes:
     skills: [yss-router]
     applies_when: frozen_scope_ready_for_slicing
     not_applicable_reason: contract_or_scope_not_frozen
+    must_complete_before: work-unit.slice-implementation
   work-unit.slice-implementation:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-router
@@ -206,6 +297,7 @@ work_unit_routes:
         theme_impact: no_theme_impact
     applies_when: ready_for_agent
     not_applicable_reason: slice_contract_not_approved
+    requires_completed_work_units: [work-unit.ticket-decomposition]
   work-unit.frontend-implementation-verification:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-ui
@@ -239,9 +331,49 @@ compatibility_flow_preconditions:
     output: vertical-slice-tickets
     output_role: ready-for-human
   implement:
-    required: [ready_for_agent, slice_contract_approved, slice_contract_persisted, slice_contract_current_version, build_architecture_checklist, implementation_repo, implementation_branch, ci, verification_commands, rollback_point, backend_slice_contract_if_applicable, backend_scaffold_policy_satisfied, frontend_implementation_plan_if_ui_impact]
+    required: [ready_for_agent, predecessor_work_unit, ticket_decomposition_result_ref, ticket_decomposition_result_status, vertical_slice_ticket_ref, vertical_slice_ticket_role, vertical_slice_ticket_kind, slice_contract_approved, slice_contract_persisted, slice_contract_current_version, build_architecture_checklist, implementation_repo, implementation_branch, ci, verification_commands, rollback_point, backend_slice_contract_if_applicable, backend_scaffold_policy_satisfied, frontend_implementation_plan_if_ui_impact]
     applies_to_single_session: true
 
+ticket_formalization:
+  implementation_predecessor: work-unit.ticket-decomposition
+  result_ref_required: true
+  result_must_be: completed
+  evidence_refs_required: true
+  vertical_slice_ticket:
+    kind: vertical-slice-ticket
+    role_before_promotion: ready-for-human
+    role_for_implementation: ready-for-agent
+    local_ref_pattern: '^docs/\\.scratch/[^/]+/issues/[^/]+\\.md$'
+    parent_ticket_ref_forbidden: true
+  slice_contract_binding:
+    ticket_ref_must_equal: vertical_slice_ticket_ref
+    status: approved
+    persisted: true
+    current_version: true
+  validator:
+    module: scripts/lib/lifecycle-transition.mjs
+    functions: [validateNextRoute, validateTicketFormalization, validateImplementationEntry]
+
+transition_graph:
+  validator: scripts/lib/lifecycle-transition.mjs
+  implementation_requires_predecessor: work-unit.ticket-decomposition
+  routes:
+    work-unit.ssot-update: [work-unit.skill-projection-sync, work-unit.intensity-aware-verification]
+    work-unit.skill-projection-sync: [work-unit.template-snapshot-build, work-unit.intensity-aware-verification]
+    work-unit.template-snapshot-build: [work-unit.attach-sync-integration, work-unit.intensity-aware-verification]
+    work-unit.attach-sync-integration: [work-unit.intensity-aware-verification]
+    work-unit.intensity-aware-verification: [work-unit.intensity-aware-review]
+    work-unit.intensity-aware-review: [work-unit.release-and-rollback]
+    work-unit.release-and-rollback: []
+    work-unit.spec-synthesis: [work-unit.prototype-design, work-unit.technical-analysis, work-unit.ticket-decomposition]
+    work-unit.prototype-design: [work-unit.technical-analysis, work-unit.ticket-decomposition]
+    work-unit.technical-analysis: [work-unit.ticket-decomposition]
+    work-unit.ticket-decomposition: [work-unit.slice-implementation]
+  forbidden_shortcuts:
+    - {from: work-unit.spec-synthesis, to: work-unit.slice-implementation}
+    - {from: work-unit.prototype-design, to: work-unit.slice-implementation}
+    - {from: work-unit.technical-analysis, to: work-unit.slice-implementation}
+
 grill_exit:
   required: [frontier_empty, facts_resolved_or_routed, decisions_confirmed, shared_understanding_confirmed, no_unresolved_runnable_blocker]
   facts_resolved_or_routed:
@@ -467,7 +599,10 @@ wayfinder_completion:
   required: [no_open_children, no_open_blocked_or_claimed_children, no_fog, destination_clear]
 
 ready_for_agent:
-  required: [gates_satisfied, no_stale_artifacts, blockers_closed, implementation_context_ready, implementation_repo, implementation_branch, ci, verification_commands, rollback_point, slice_contract_approved, slice_contract_persisted, slice_contract_current_version, build_architecture_checklist, backend_slice_contract_if_applicable, backend_scaffold_policy_satisfied, frontend_implementation_plan_if_ui_impact]
+  required: [gates_satisfied, no_stale_artifacts, blockers_closed, implementation_context_ready, implementation_repo, implementation_branch, ci, verification_commands, rollback_point, predecessor_work_unit, ticket_decomposition_result_ref, ticket_decomposition_result_status, vertical_slice_ticket_ref, vertical_slice_ticket_role, vertical_slice_ticket_kind, slice_contract_approved, slice_contract_persisted, slice_contract_current_version, build_architecture_checklist, backend_slice_contract_if_applicable, backend_scaffold_policy_satisfied, frontend_implementation_plan_if_ui_impact]
+  ticket_formalization_validator: scripts/lib/lifecycle-transition.mjs
+  requires_vertical_slice_ticket: true
+  parent_ticket_as_implementation_ref: forbidden
 
 frontend_implementation_plan:
   applies_when: [ui_impact]

package/template/.codex/skills/yss-product-lifecycle/references/orchestration.md

@@ -5,8 +5,8 @@
 1. 识别模式、仓库身份、任务规模和影响面。
 2. `setup readiness`：每个任务只执行一次，核对 tracker、五态标签和领域文档布局，并在本轮缓存结果；仅在 tracker、主远端、真实标签或配置变化时重查。
 3. 加载父 Ticket/checkpoint 与真实资产，计算最近可信阶段。
-4. 评估资产、门禁和 `stale`，选择第一个未阻塞工作单元。
-5. 执行最小生命周期工作单元：只实际调用允许的 model-invoked skill；原生工作单元可直接持有正式资产，Matt 兼容 user-invoked skill 仅作为 workflow reference，仍由用户显式启动。将结果归一化为 `Workflow Execution Result`，验收输出并回写状态与证据。
+4. 评估资产、门禁和 `stale`，选择第一个未阻塞工作单元。进入 `work-unit.slice-implementation` 前，必须先通过 `scripts/lib/lifecycle-transition.mjs` 的 Ticket 正式化、垂直切片绑定和合法 `next_route` 校验；父 Ticket、缺少垂直切片或 `ready-for-human` 的切片一律 `blocked`。
+5. 执行最小生命周期工作单元：主控先按 `docs/process/schemas/digital-human-task-package.schema.json` 编译并校验任务包，再只实际调用允许的 model-invoked skill；原生工作单元可直接持有正式资产，Matt 兼容 user-invoked skill 仅作为 workflow reference，仍由用户显式启动。将结果归一化为 `Workflow Execution Result`，验收输出并回写状态与证据。任务包的 `contract.kind` 按工作单元选择；只有实现子任务使用 `slice-implementation` 并消费 Slice Implementation Contract，其他阶段不伪造该合同。
 6. 若仍在授权和自动推进边界内，回到第 3 步；否则暂停。
 
 不要仅输出下一个提示词后结束 `orchestrate`/`resume`。不要因进入业务代码阶段而退出主控；应把实现交给专项 skill，并在返回后继续核验。
@@ -51,9 +51,12 @@ tracker 选择和冲突按 `docs/agents/issue-tracker.md` 裁决：已持久化
 
 ## Matt flow 进入条件
 
+- `work-unit.technical-analysis` 命中聚合、状态机、不变量、一致性、Domain Event、Gateway 或持久化映射影响时，先调度 `yss-tactical-design` 完成 Tactical DDD Check；默认嵌入系统概要设计 / 数据架构，复杂场景才生成 `artifact.tactical-design`。无领域影响记录 `not-applicable`。该 skill 只返回设计合同和验证结果，批准仍由生命周期编排器维护，发现 `stale`、`drift` 或 `new_impacts` 时不得继续 Ticket 正式化。
+
 - `work-unit.discovery-requirements` 实际调用 `grilling` 和 `domain-modeling`；`work-unit.discovery-opportunity` 按事实类型路由 `competitive-intelligence` 或 `research`。生命周期原生工作单元默认负责 Spec、Ticket 和实现资产；`to-spec`、`to-tickets`、`implement` 仅保留为显式兼容入口，结果必须回交生命周期验收。
-- 原生 `work-unit.ticket-decomposition` 只能在 OpenAPI Freeze 或无 API 影响记录后创建垂直切片，初始角色统一为 `ready-for-human`；生命周期复算完整公式后才能提升 `ready-for-agent`。
+- 原生 `work-unit.ticket-decomposition` 只能在 OpenAPI Freeze 或无 API 影响记录后创建垂直切片，初始 Ticket 状态统一为 `ready-for-human`；生命周期复算完整公式后才能提升 `ready-for-agent`。该工作单元必须返回 `ticket_decomposition_result_ref` 和垂直切片引用，并作为实现的必经前置证据。
 - 原生 `work-unit.slice-implementation` 必须在生命周期批准并持久化 Slice Implementation Contract 和 Build Architecture Checklist 后执行；用户显式 `implement` 仍走兼容入口，不得绕过生命周期。
+- `Workflow Execution Result.next_route` 必须通过生命周期转换校验；Spec、原型和技术分析不得直接跳转到 `work-unit.slice-implementation`，只能先进入 `work-unit.ticket-decomposition`。
 - `implement` 遇到 backend `scaffold_status=required` 时，还必须满足原型确认后的脚手架策略：脚手架 Execution Result、`yss-backend-scaffold-parent` 基线、Wrapper 验证和 Router 合同重编译均已回写；否则停在工程基线，不得写业务代码。
 - `Workflow Execution Result` 出现 `drift`、`new_impacts`、`stale_candidates`、`violation`、`missing_evidence`、空 `evidence_refs` 或缺少必需字段时暂停当前工作单元；旧结果只能先经只读兼容 adapter 归一化。
 
@@ -73,13 +76,13 @@ tracker 选择和冲突按 `docs/agents/issue-tracker.md` 裁决：已持久化
 
 ## 必须暂停
 
-- Spec baseline、需求冻结、原型确认、OpenAPI Freeze 或 Architecture Review 等普通门禁等待人工裁决。
+- Spec baseline、需求冻结、原型确认、OpenAPI Freeze 或 Architecture Review 等普通门禁等待会签裁决（数字人或生物人，以 `docs/agents/digital-human-roles.yaml` 的 `gate_policy` 为准）。暂停输出必须包含：门禁 ID、指定 `role_id`、`runtime_id`、会签文件路径。恢复前执行 `scripts/verify-approval-record`；角色错误、起草者自签或生物人门禁被数字人关闭时返回 `blocked`，不得标 `approved`。
 - 需要目标仓库、外部凭据、发布窗口或其他新授权。
 - 状态与证据冲突且无法可靠重建。
 - 专项 skill 失败或返回不可验收结果。
 - 即将作出可合并、可发布或完成结论。
 
-暂停输出：门禁、证据、责任人、推荐答案、一个问题、恢复动作。
+暂停输出：门禁、指定会签 `role_id`、`runtime_id`、会签文件路径、证据、推荐答案、一个问题、恢复动作。
 
 ## Wayfinder 完成判定
 

package/template/.codex/skills/yss-product-lifecycle/references/state-model.md

@@ -11,7 +11,7 @@
 | `tracker.kind` | `local-markdown`、`github`、`gitlab` |
 | `ticket.role` | `needs-triage`、`needs-info`、`ready-for-agent`、`ready-for-human`、`wontfix` |
 
-Matt 五态不得扩义。资产的 `ready-for-human` 与 Ticket label 必须带命名空间表达。
+Matt 五态不得扩义。资产的 `ready-for-human` 与 Ticket label 必须带命名空间表达。`paused-human-gate` 表示等待 `docs/agents/digital-human-roles.yaml` 指定的会签人（数字人或生物人），不是「必须是生物人」。
 
 ## 上下文与外部输入证据
 
@@ -34,14 +34,19 @@ phase_boundary:
 
 ## `ready-for-agent` 公式
 
-仅当以下全部为真，垂直切片 Ticket 才能获得该角色：
+仅当以下全部为真，垂直切片 Ticket 才能获得该 Ticket 状态：
 
 ```text
 required gates ∈ {approved, not-applicable}
-AND related artifacts 不含 stale
+AND related artifacts 不含 stale（若命中领域影响，`artifact.tactical-design` 或嵌入式 Tactical DDD Check 引用必须为当前版本）
 AND blocking edges 全部关闭
 AND implementation repo/branch/CI/test/rollback 已明确
+AND `work-unit.ticket-decomposition` 已返回 `completed`，且其 `ticket_decomposition_result_ref` 证据可读取
+AND `vertical_slice_ticket_ref` 指向 `docs/.scratch/<feature>/issues/` 下的垂直切片 Ticket
+AND `vertical_slice_ticket_kind=vertical-slice-ticket` 且 `vertical_slice_ticket_role=ready-for-agent`
+AND `vertical_slice_ticket_ref` 不得指向 `parent-ticket.md`
 AND Slice Implementation Contract 已由生命周期编排器批准并持久化
+AND Slice Implementation Contract 的 `ticket_ref` 与 `vertical_slice_ticket_ref` 完全一致
 AND 当前工作单元消费的 contract_id/version 与最新批准版本一致
 AND Backend Slice Implementation Contract（后端适用）和 Build Architecture Checklist 已完成
 AND backend 影响且 scaffold_status=required 时，原型确认后的脚手架策略、`yss-backend-scaffold-parent` 基线、Wrapper 验证和 Router 重编译均已完成
@@ -53,7 +58,7 @@ AND UI 影响切片的前端实现还原计划已通过 schema 校验、`templat
 
 发布前还必须满足所有已触发门禁均为 `approved` 或 `not-applicable`；UI 影响切片必须额外通过 `gate.frontend-implementation-verified`，不能只凭 fresh verification 和回滚点放行。
 
-用户显式运行 `to-tickets` 后，垂直切片初始角色固定为 `ready-for-human`。只有 `yss-product-lifecycle` 复算上述公式全部为真后，才能把它提升为 `ready-for-agent`；生命周期不会自动调用 `to-tickets`，其默认标签也不参与该裁决。
+用户显式运行 `to-tickets` 后，垂直切片初始 Ticket 状态固定为 `ready-for-human`。原生路径执行 `work-unit.ticket-decomposition` 时同样必须产生等价的垂直切片和 `Workflow Execution Result` 证据。只有 `yss-product-lifecycle` 复算上述公式全部为真后，才能把它提升为 `ready-for-agent`；生命周期不会自动调用 `to-tickets`，但不得跳过 Ticket 正式化工作单元。其默认标签也不参与该裁决。
 
 ## Review 与 Git 授权状态
 

package/template/.codex/skills/yss-router/SKILL.md

@@ -13,20 +13,21 @@ description: Use when a YSS vertical slice is entering implementation, spans mul
 
 ## 编译循环
 
-1. 判断 frontend/backend/API/data/cross-repo 影响，并逐项填写 backend `component_impacts`。
+1. 判断 frontend/backend/API/data/domain/cross-repo 影响，并逐项填写 backend `component_impacts`；命中聚合、状态机、不变量、一致性、Domain Event、Gateway 或持久化映射时加入 `yss-tactical-design`。
 2. 检查工程存在性和核心/长尾 skill 可用性。
 3. 选择主 skill，并按 [router-contract.yaml](references/router-contract.yaml) 计算强制依赖闭包。
 4. 为切片生成基线合同；为当前行为生成工作单元增量路由。
 5. 选择 `behavior-tdd` 或 `controlled-generation`。
 6. 输出 `draft`、`blocked` 或 `ready-for-lifecycle-review`，交生命周期编排器核验和持久化。
 
-合同结构见 [slice-implementation-contract.md](references/slice-implementation-contract.md)，专项返回协议见 [yss-skill-execution-result.md](references/yss-skill-execution-result.md)。
+合同结构见 [slice-implementation-contract.md](references/slice-implementation-contract.md)，专项返回协议见 [yss-skill-execution-result.md](references/yss-skill-execution-result.md)。前端、后端和测试子任务必须由生命周期主控从批准的 Slice Contract 编译任务包；任务包 schema 为 `docs/process/schemas/subagent-task-package.schema.json`，技能列表必须来自 `taskPackageDefaults`，不能由 Router 或执行 Agent 另行手写。
 
 ## 硬规则
 
 - Router 不得输出 `approved`、`ready-for-agent` 或 `completed`。
 - UI 影响缺少正式原型确认时，不得路由页面实现。
 - Repository/数据模型影响缺少数据架构时，不得路由持久化实现。
+- 领域影响缺少批准且版本当前的 tactical-design contract 时，不得路由 Domain 实现；无领域影响必须记录 `not-applicable`。
 - API 变化必须回到生命周期 Draft/Review/Freeze；半成品 backend 不得冒充稳定 source of truth。
 - 后端端到端切片必须包含 Application；对象/POJO 影响按契约自动补 `mapstruct`、`lombok`、`alibaba-java-code-style`。
 - Harness 内实现路径必须落在 `apps/backend/<project>/` 或 `apps/frontend/<project>/` 的具体项目目录；`apps/backend/`、`apps/frontend/` 只能作为容器，`app/backend/`、`app/frontend/` 及其子路径一律阻断。外部实现仓库使用其登记的真实项目根路径。`git-submodule` 使用 `implementation_path_policy: git-submodule-harness-apps`，空 gitlink、detached HEAD 或 `--force` 覆盖挂载点不得脚手架；`inspectWorkingTreeScope.writable` 必须为显式布尔值。
@@ -36,6 +37,7 @@ description: Use when a YSS vertical slice is entering implementation, spans mul
 - 脚手架合同在 Router 阶段只能是 `draft` / `ready-for-lifecycle-review` / `blocked`；只有生命周期编排器可以把已持久化脚手架合同标记为 `approved`。脚手架合同只覆盖业务代码前的工程骨架工作单元；生成、基线校验和 Router 重编译完成后，它不能替代脚手架后的 Slice Implementation Contract。
 - 脚手架输出消费批准的脚手架合同；脚手架后的所有生成后端代码都必须绑定当前批准且版本当前的 Slice Implementation Contract、主 YSS skill、依赖闭包、允许写路径、预期证据和 YSS Skill Execution Result。打印命令、`./mvnw validate` 单项通过或脚手架成功不能替代合同批准；生成范围从机械内容变成业务行为时触发完整重路由。
 - 专项结果中的越界路径、缺失证据、`drift`、`violation` 或 `new_impacts` 必须阻断或重路由。
+- 前后端子任务必须使用同一 `contract_id/contract_version`，并在任务包中记录 `role_id`、`runtime_id`、`execution_state`、`allowed_write_paths`、`downstream_consumers` 和 `convergence_ref`；版本不一致或汇合引用缺失时输出 `blocked`。
 - 长尾 skill 不可用时显式 `blocked`，不得用通用知识假装已应用 YSS 规范。
 
 ## 三级路由
@@ -46,4 +48,4 @@ description: Use when a YSS vertical slice is entering implementation, spans mul
 
 ## 输出
 
-输出合同草案、技能依赖闭包、不适用理由、阻塞项、TDD 模式、工作单元、预期证据、验证命令、人工审查点和完整重路由触发器。自然语言说明不能替代结构化合同字段。
+输出合同草案、技能依赖闭包、不适用理由、阻塞项、TDD 模式、工作单元、预期证据、验证命令、人工审查点、完整重路由触发器，以及建议的 `suggested_owner_role_id`（UI 影响 → `role.frontend-engineer`，后端影响 → `role.backend-engineer`，测试/审查 → `role.test-engineer`）。自然语言说明不能替代结构化合同字段。Router 不得自行批准合同、设置 `ready-for-agent` 或关闭会签门禁；owner 建议只供主控派活。

package/template/.codex/skills/yss-router/references/router-contract.yaml

@@ -66,11 +66,11 @@ exclusive_flags:
 
 slice_contract_required:
   root: [schema_version, contract_id, contract_version, slice_id, status, lifecycle_refs, readiness, common, frontend, backend, contract, cross_repo, work_units]
-  lifecycle_refs: [spec, ticket, requirement_freeze, low_fidelity_review, prototype_review, high_fidelity_html, prototype_verification, antd_cli_evidence, browser_verification_evidence, prototype_confirmation, openapi_freeze_or_no_impact, architecture_review, data_architecture, engineering_baseline, build_architecture_checklist, implementation_repository, frontend_repository, backend_repository, maven_wrapper]
+  lifecycle_refs: [spec, ticket, requirement_freeze, low_fidelity_review, prototype_review, high_fidelity_html, prototype_verification, antd_cli_evidence, browser_verification_evidence, prototype_confirmation, openapi_freeze_or_no_impact, architecture_review, data_architecture, tactical_design, engineering_baseline, build_architecture_checklist, implementation_repository, frontend_repository, backend_repository, maven_wrapper]
   readiness: [blockers, stale_inputs, not_applicable]
   common: [impacted_areas, implementation_path_policy, project_roots, required_skills, optional_skills, unavailable_skills, allowed_write_paths, forbidden_patterns, expected_evidence_files, verification_commands, human_review_points, full_reroute_triggers]
   frontend: [status, required_skills, approved_prototype_ref, state_matrix_ref, allowed_write_paths, component_test_seams, e2e_paths]
-  backend: [status, affected_layers, component_impacts, required_skills, application_boundary, transaction_boundary, persistence_strategy, allowed_write_paths, forbidden_patterns, expected_evidence_files, seam_deferred, verification_commands]
+  backend: [status, affected_layers, component_impacts, required_skills, application_boundary, transaction_boundary, persistence_strategy, allowed_write_paths, forbidden_patterns, expected_evidence_files, seam_deferred, verification_commands, tactical_ddd]
   contract: [api_impact, freeze_ref, no_api_impact_ref, generated_clients, contract_tests, regeneration_commands]
   cross_repo: [repositories, delivery_order, integration_verification, rollback_order]
 
@@ -91,6 +91,7 @@ lifecycle_ref_by_readiness:
   openapi_freeze: openapi_freeze_or_no_impact
   no_api_impact_record: openapi_freeze_or_no_impact
   data_architecture: data_architecture
+  tactical_design: tactical_design
   engineering_baseline: engineering_baseline
   backend_repository: backend_repository
   maven_wrapper: maven_wrapper
@@ -135,6 +136,10 @@ applicable_subcontract_nonempty:
   backend:
     scalar: [application_boundary, transaction_boundary, persistence_strategy]
     array: [affected_layers, required_skills, allowed_write_paths, forbidden_patterns, expected_evidence_files, verification_commands]
+    conditional_tactical_ddd:
+      when: [aggregate-impact, state-machine-impact, invariant-impact, consistency-impact, domain-event-impact, gateway-boundary-impact, persistence-mapping-impact]
+      scalar: [tactical_design_ref, tactical_design_version, gateway_boundary_ref]
+      array: [aggregate_refs, invariant_refs, state_behavior_refs, domain_test_seams, application_test_seams]
   contract_api:
     scalar: [freeze_ref]
     array: [contract_tests]
@@ -148,8 +153,12 @@ dependency_closure:
     always: [yss-backend-scaffold-parent, alibaba-java-code-style]
   yss-domain:
     always: [alibaba-java-code-style]
-    when_modeling: [domain-modeling]
+    when_modeling: [domain-modeling, yss-tactical-design]
     when_pojo: [lombok]
+  yss-tactical-design:
+    always: [domain-modeling]
+    when_api_impact: [yss-openapi-draft-review]
+    when_data_impact: [yss-repository]
   yss-application:
     always: [alibaba-java-code-style]
     when_conversion: [mapstruct, lombok]
@@ -218,6 +227,12 @@ full_reroute_triggers:
   - data-model-impact
   - new-write-path
   - new-repository
+  - aggregate-impact
+  - invariant-impact
+  - consistency-impact
+  - domain-event-impact
+  - gateway-boundary-impact
+  - persistence-mapping-impact
   - new-required-skill
   - not-applicable-invalidated
   - architecture-drift

package/template/.codex/skills/yss-router/references/slice-implementation-contract.md

@@ -9,6 +9,7 @@ slice_contract:
   contract_version: 1
   slice_id:
   status: draft
+  suggested_owner_role_id: # role.frontend-engineer | role.backend-engineer | role.test-engineer；Router 只建议，编排器派活并批准
   lifecycle_refs:
     spec:
     ticket:
@@ -24,6 +25,7 @@ slice_contract:
     architecture_review:
     data_architecture:
     engineering_baseline:
+    tactical_design:
     build_architecture_checklist:
     implementation_repository:
     frontend_repository:
@@ -69,6 +71,24 @@ slice_contract:
     application_boundary:
     transaction_boundary:
     persistence_strategy:
+    tactical_design_ref:
+    tactical_design_version:
+    aggregate_refs: []
+    invariant_refs: []
+    state_behavior_refs: []
+    gateway_boundary_ref:
+    domain_test_seams: []
+    application_test_seams: []
+    tactical_ddd:
+      status: not-applicable
+      tactical_design_ref:
+      tactical_design_version:
+      aggregate_refs: []
+      invariant_refs: []
+      state_behavior_refs: []
+      gateway_boundary_ref:
+      domain_test_seams: []
+      application_test_seams: []
     allowed_write_paths: []
     forbidden_patterns: []
     expected_evidence_files: []
@@ -86,7 +106,43 @@ slice_contract:
     delivery_order: []
     integration_verification: []
     rollback_order: []
-  work_units: []
+  work_units:
+    - id: slice-frontend
+      role_id: role.frontend-engineer
+      runtime_id: runtime.skill-projection
+      execution_state: Worker
+      workflow_status: not-started
+      task_package_ref:
+      contract_id: # must equal slice_contract.contract_id
+      contract_version: # must equal slice_contract.contract_version
+      downstream_consumers: []
+      convergence_ref:
+      work_unit:
+        behavior:
+        primary_skill:
+        supporting_skills: []
+        tdd_mode: behavior-tdd
+        allowed_write_paths: []
+        expected_evidence: []
+        verification_commands: []
+    - id: slice-backend
+      role_id: role.backend-engineer
+      runtime_id: runtime.skill-projection
+      execution_state: Worker
+      workflow_status: not-started
+      task_package_ref:
+      contract_id:
+      contract_version:
+      downstream_consumers: []
+      convergence_ref:
+      work_unit:
+        behavior:
+        primary_skill:
+        supporting_skills: []
+        tdd_mode: behavior-tdd
+        allowed_write_paths: []
+        expected_evidence: []
+        verification_commands: []
 ```
 
 工作单元：
@@ -111,3 +167,5 @@ work_unit:
 ```
 
 `controlled_generation` 仅在 `tdd_mode: controlled-generation` 时必填；其他模式标记 `not-applicable`。明确写入需求的权限业务行为仍使用 `behavior-tdd`；API schema 与 database schema 分别触发契约或数据架构回退，不得用一个含糊的 schema 类型决定路线。
+
+`work_units` 中的前端、后端和测试任务是切片级子任务，不是新的生命周期阶段。每个子任务必须引用独立任务包；任务包只能消费同一份已批准且版本当前的 Slice Contract。`workflow_status` 追踪执行过程，不能替代生命周期状态；`contract_id` 或 `contract_version` 不一致时必须阻断并回到 Router。

package/template/.codex/skills/yss-stage-decision/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: yss-stage-decision
+description: 编排 Discovery 到 Spec 入口的阶段决策与 DDD 战略设计；当需求、领域边界、统一语言或下游影响尚未稳定时使用。
+---
+
+# YSS Stage Decision
+
+`yss-stage-decision` 是由 `yss-product-lifecycle` 调度的上游决策技能空间，负责把需求、产品、商务输入和 DDD 战略设计结果整理成可审查、可版本化、可被下游消费的阶段决策包。它不替代生命周期主控，也不生成产品代码、原型、OpenAPI 或垂直切片 Ticket。
+
+## 适用边界
+
+- 适用于 `project-instance` 的 Discovery → Spec 入口。
+- `template-source` 只维护本技能、Schema、验证器和合成 Fixture，不生成具体产品领域资产。
+- DDD 工作单元只做子域、限界上下文、Context Map、统一语言、关键场景、事件、核心领域概念候选和业务不变量。
+- Entity、Aggregate、Repository、Java 类、数据库表和 OpenAPI Freeze 留给下游工作单元。
+
+## 执行顺序
+
+1. 读取 `yss-project.yaml`、`CONTEXT.md`、既有 Discovery/Spec、ADR 和父 Ticket/checkpoint。
+2. 分离事实、决策、假设、约束和未决项；技术事实走 `research`，市场/竞品事实走 `competitive-intelligence`。
+3. 从业务场景、事件、规则、责任人和失败路径识别子域及限界上下文，不从数据库表或调用链直接反推边界。
+4. 为每个上下文建立本地统一语言；为跨上下文关系记录语义上游/下游、业务决策权、技术传输方向和翻译责任。
+5. 记录核心领域概念候选，不提前锁定 Entity 或 Aggregate。
+6. 生成 `domain_strategy` 和 `stage_decision_package`，绑定版本、digest、证据和下游影响映射。
+7. 运行 Schema、引用、语义一致性和传播验证；发现关键冲突时返回 `blocked`，不得生成 `approved` 包。
+
+## 语义方向规则
+
+`semantic_upstream` 是拥有业务规则、决策语义或权威模型的一方；`semantic_downstream` 是消费、适配或依赖该语义的一方。二者不等于 HTTP、事件或数据库的技术方向。每条 Context Map 关系必须独立记录 `transport_direction` 和 `translation_responsibility`；同一对上下文可以存在多条相反方向的语义边。
+
+## 产物与批准
+
+- DDD 资产是事实源，阶段决策包只通过 `domain_strategy_ref` 引用它们。
+- `stage_decision_package` 必须经过 `draft → ready-for-human → approved`；起草者不得自签。
+- 建议门禁为 `gate.domain-strategy-approved` 和 `gate.stage-decision-package-approved`，实际状态由 `yss-product-lifecycle` 维护；阶段包批准引用必须通过 `scripts/verify-approval-record`，不得用不可读路径或聊天确认替代。
+- 下游只能消费批准且版本当前的包；发现语义冲突返回 `drift` / `new_impacts`，不得静默修改上游。
+
+## 结果合同
+
+返回标准 `Workflow Execution Result`，至少包含 `work_unit`、`workflow_reference`、`result`、`evidence_refs`、`changed_artifacts`、`new_impacts`、`stale_candidates`、`next_route` 和 `blocking_signals`。`blocked` 必须包含冲突、责任人、恢复条件和下一工作单元。
+
+## 禁止事项
+
+- 不把阶段包当作第二套领域事实源。
+- 不按数据库、微服务、菜单或 HTTP 调用方向自动划分上下文。
+- 不把同名术语强行合并为全局概念。
+- 不在战略设计阶段生成 Entity、Aggregate、Repository、生产代码或 API 契约。
+- 不把模板 Fixture 当作具体项目的业务事实。
+
+详细合同、字段和验证规则见 `references/domain-strategy-contract.md`、`references/stage-decision-package-contract.md` 与 `references/validation-rules.md`。机器可读合同分别为 `references/domain-strategy.schema.json` 和 `references/stage-decision-package.schema.json`；对应验证器为 `scripts/validate-domain-strategy.mjs` 与 `scripts/validate-stage-decision-package.mjs`。

package/template/.codex/skills/yss-stage-decision/references/domain-strategy-contract.md

@@ -0,0 +1,26 @@
+# DDD 战略设计合同
+
+## 顶层结构
+
+机器可读合同使用 `references/domain-strategy.schema.json`。顶层必须包含：
+
+- `schema_version`、`domain_strategy_id`、`domain_version`、`status`；
+- `contexts`、`subdomains`、`relationships`、`scenarios`；
+- `concept_candidates`、`invariants`、`terminology_refs`；
+- `downstream_mapping`、`evidence_refs`、`approval`。
+
+## 上下文
+
+每个上下文声明 `context_id`、职责边界、非职责、子域分类、模型所有者、关键场景和本地词汇引用。`context_id` 是稳定身份，不得使用代码模块、数据库 schema 或菜单路径替代。
+
+## 关系
+
+关系必须声明 `relationship_pattern`、`semantic_upstream`、`semantic_downstream`、`business_authority`、`model_change_impact`、`transport_direction` 和 `translation_responsibility`。语义方向与技术方向可以不同；关系模式只能使用合同中列出的 DDD 模式。
+
+## 核心概念
+
+使用 `domain_concept_candidate` 表达战略阶段的核心概念候选，记录身份特征、生命周期、不变量引用、可能的战术角色和置信度。不得在该合同中把概念直接批准为 Entity 或 Aggregate Root。
+
+## 阶段决策包
+
+阶段包应通过 `domain_strategy_ref` 引用 DDD 合同的当前版本和 digest，并使用 `domain_to_downstream_mapping` 描述领域变化对 Spec、设计、API、数据、Ticket 和测试 seam 的传播。