create-yss-spec 3.3.0 → 3.3.3

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

@@ -48,6 +48,91 @@ modes:
   orchestrate: bounded_write
   resume: rebuild_then_bounded_write
 
+# 用户请求理解与动作选择的唯一判断合同；自然语言解释由主控完成。
+request_triage:
+  owner: yss-product-lifecycle
+  interpretation:
+    inputs: [current-request, conversation-context, accessible-evidence]
+    capture: [goal, target, expected-deliverable, action-scope, facts, assumptions, unknowns]
+    multiple_intents: preserve-all-goals-and-order-dependencies
+    competing_interpretations: compare-effect-on-next-action
+    numeric_self_confidence: forbidden-as-routing-evidence
+  clarification:
+    trigger: missing-information-changes-next-action-or-authorization-scope
+    before_asking: reuse-context-and-inspect-accessible-evidence
+    short_request_alone: insufficient-reason-to-ask
+    question: explain-gap-and-ask-minimum-actionable-information
+    batch: independent-current-decision-questions
+    same_safe_next_step: investigate-before-asking
+    user_cannot_answer: narrow-problem-or-offer-bounded-guidance-keep-unresolved
+    timeout_is_answer: false
+  mode_selection:
+    priority: [explicit-current-restriction, authorized-continuation, clear-action-request, read-only-fallback]
+    explicit_read_only: route
+    explicit_audit: audit
+    authorized_continuation: resume
+    clear_action_request: orchestrate
+    unresolved_intent: route
+    investigation: read-only-actions-unless-additional-scope-authorized
+    mode_keywords_required: false
+    continuation: revalidate-scope-evidence-and-applicable-gates
+    gates_and_external_authorization: unchanged
+  next_action:
+    consultation: answer
+    investigation: inspect-evidence
+    action_request: execute-first-authorized-unblocked-work-unit
+    material_ambiguity: clarify
+    missing_prerequisite: explain-blocker-and-continue-independent-authorized-work
+    skill_name_only_is_completion: false
+  correction:
+    stop: actions-dependent-on-invalid-interpretation
+    preserve: still-valid-evidence-and-unrelated-user-work
+    report: revised-goal-and-actions-already-taken
+    existing_edits: explain-scope-and-agree-disposition-no-blind-rollback
+    recompute: [intent, scope, impacts, freshness, next-action]
+  acceptance:
+    per_goal: [requested-outcome, readable-evidence, unresolved-items]
+    mismatch: investigate-or-reroute
+    unresolved_triage_is_complete: false
+  presentation:
+    simple: direct-answer-or-action
+    complex: brief-goal-and-next-action
+    material_ambiguity: targeted-question
+    full_workflow_record: applicable-work-units-only
+  evaluation:
+    scenarios_ref: .agents/skills/yss-product-lifecycle/references/request-triage-scenarios.yaml
+    dimensions: [understanding-error, wrong-route, unnecessary-question, omitted-intent, post-triage-stall, correction-failure]
+    baseline: required-before-numeric-improvement-claim
+    structural_checks_prove_model_accuracy: false
+
+execution_efficiency:
+  context_query:
+    strategy: combine-mode-stage-work-unit-and-required-includes
+    read_scope: current-work-unit-and-triggered-impacts
+    reuse: already-read-unchanged-sources-within-current-task
+    refresh_on: [source-changed, new-impact, evidence-conflict, resume, handoff]
+  verification:
+    scope: current-artifacts-and-triggered-contracts
+    timing: after-artifact-write-before-approval-or-transition
+    duplicate_check: reuse-only-within-same-boundary-and-unchanged-inputs
+    unchanged_inputs: [artifact-bytes, upstream-bytes, validator-and-schema, command-and-options, repository-root]
+    freshness_unknown: rerun
+    always_revalidate_on: [resume, handoff, implementation-entry, merge, release]
+    template_regression_suite: template-maintenance-or-explicit-regression-task
+    per_work_unit_context_reconciliation: required
+    skip_triggered_gates: forbidden
+  interaction:
+    questions: batch-independent-current-stage-questions
+    user_decision_policy_ref: docs/agents/digital-human-roles.yaml#user_decision_policy
+    decision_evidence_ref: references/user-decisions.md
+    dependent_future_approvals: forbidden
+    checkpoint_policy_ref: checkpoint_policy
+  timing_evidence:
+    location: existing-checkpoint-verification-evidence
+    script_fields: [command, duration_ms, exit_code]
+    distinguish: [script-execution, agent-orchestration, human-wait]
+    unmeasured_duration: unknown
+
 # 有效的 YSS 仓库必须先由生命周期编排器接管入口；Matt flow 只负责选择工作方式。
 entry_routing:
   manifest: yss-project.yaml
@@ -210,7 +295,7 @@ lifecycle_native_entries:
     implement: lifecycle-validate-and-accept
 
 work_unit_routes:
-  work-unit.discovery-opportunity:
+  work-unit.plan-opportunity:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-product-lifecycle
     supporting_skills: [competitive-intelligence, yss-research]
@@ -218,7 +303,7 @@ work_unit_routes:
     route_by: {market_or_competitor_fact: competitive-intelligence, technical_or_standard_fact: yss-research:technical-evidence, strategy_fact: yss-research:strategy-evidence, no_external_fact: yss-product-lifecycle}
     applies_when: opportunity_or_external_fact_requires_validation
     not_applicable_reason: no_external_fact
-  work-unit.discovery-requirements:
+  work-unit.plan-requirements:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
     primary_skill: yss-product-lifecycle
     supporting_skills: [grilling, domain-modeling]
@@ -231,7 +316,7 @@ work_unit_routes:
     supporting_skills: [domain-modeling, yss-research, grilling]
     skills: [yss-stage-decision, domain-modeling, yss-research, grilling]
     research_contract: {profile: strategy-evidence, mode_before_gate: evidence-audited, artifact_owner: yss-research, downstream_owner: yss-stage-decision}
-    human_gate: domain-strategy-approved
+    internal_review: check.domain-strategy-approved
     applies_when: domain_boundary_or_language_or_core_rule_impact
     not_applicable_reason: no_domain_strategy_impact
   work-unit.stage-decision:
@@ -240,8 +325,8 @@ work_unit_routes:
     supporting_skills: [domain-modeling, yss-research]
     skills: [yss-stage-decision, domain-modeling, yss-research]
     research_contract: {profile: strategy-evidence, mode_before_gate: evidence-audited, artifact_owner: yss-research, downstream_owner: yss-stage-decision}
-    human_gate: stage-decision-package-approved
-    applies_when: discovery_to_spec_requires_stable_decision_package
+    internal_review: check.stage-decision-package-approved
+    applies_when: plan_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}
@@ -269,7 +354,7 @@ work_unit_routes:
         H2: {kind: flow-review, adapter: runnable-flow, react_antd: supported-not-required, antd_facts: conditional}
     implementation_handoff: {production_component_assumptions: required-array, verification_targets: frontend-implementation-only}
     version_boundary: {h2_design_standard: vue-antdv-next-default-react-antd-explicit-compatibility, prototype_must_not_call: yss-ui, production_version_source: implementation-lockfile}
-    human_gate: prototype-confirmation
+    human_gate: gate.product-design-approved
     applies_when: product_design_impact
     not_applicable_reason: no_ui_or_product_design_impact
   work-unit.technical-analysis:
@@ -291,7 +376,7 @@ work_unit_routes:
       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
+    human_gate: gate.engineering-contract-approved
     applies_when: technical_or_contract_impact
     not_applicable_reason: no_technical_or_contract_impact
   work-unit.implementation-repository-preparation:
@@ -303,7 +388,7 @@ work_unit_routes:
     not_applicable_reason: no_frontend_or_backend_delivery_impact
     decision_boundary: scaffold-choice
     completion_states: [existing-and-onboarded, initialized-and-verified, not-applicable]
-    aggregate_gate: gate.implementation-repositories-ready
+    automatic_check: check.implementation-repositories-ready
     must_complete_before: work-unit.ticket-decomposition
   work-unit.ticket-decomposition:
     native: {source: yss-product-lifecycle, skill: yss-product-lifecycle, invocation_mode: model-invoked}
@@ -405,7 +490,8 @@ work_unit_routes:
     primary_skill: yss-product-lifecycle
     supporting_skills: []
     skills: [yss-product-lifecycle]
-    human_gate: merge_or_release
+    acceptance_gate: gate.delivery-accepted
+    external_action_authorization: explicit_merge_or_release_only
     applies_when: release_or_stage_completion
     not_applicable_reason: work_not_ready_for_release
 
@@ -446,7 +532,7 @@ ticket_formalization:
 implementation_repository_preparation:
   stage: stage.system-data-engineering
   work_unit: work-unit.implementation-repository-preparation
-  gate: gate.implementation-repositories-ready
+  check: check.implementation-repositories-ready
   applies_per_delivery_role: [backend, frontend]
   affected_role_allowed_states: [existing-and-onboarded, initialized-and-verified]
   unaffected_role_state: not-applicable
@@ -484,6 +570,10 @@ transition_graph:
     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.plan-opportunity: [work-unit.plan-requirements, work-unit.domain-strategy-design, work-unit.stage-decision, work-unit.spec-synthesis]
+    work-unit.plan-requirements: [work-unit.domain-strategy-design, work-unit.stage-decision, work-unit.spec-synthesis]
+    work-unit.domain-strategy-design: [work-unit.stage-decision, work-unit.spec-synthesis]
+    work-unit.stage-decision: [work-unit.spec-synthesis]
     work-unit.spec-synthesis: [work-unit.prototype-design, work-unit.technical-analysis, work-unit.implementation-repository-preparation]
     work-unit.prototype-design: [work-unit.technical-analysis, work-unit.implementation-repository-preparation]
     work-unit.technical-analysis: [work-unit.implementation-repository-preparation]
@@ -495,6 +585,25 @@ transition_graph:
     - {from: work-unit.technical-analysis, to: work-unit.slice-implementation}
     - {from: work-unit.technical-analysis, to: work-unit.ticket-decomposition}
 
+planning:
+  entry_validator: scripts/verify-plan-spec-entry
+  review_contract: docs/plan/entry-review.md
+  check_policy: docs/process/lifecycle-registry.yaml
+  default_check_status: pending
+  formal_spec_draft_requires_passed_entry: true
+  stage: stage.plan
+  record: artifact.plan-record
+  template: docs/plan/templates/plan-template.md
+  exit_policy: docs/process/lifecycle-registry.yaml
+  migration_policy: docs/process/plan-migration.md
+  critical_open_questions: block-before-spec
+  deferred_details_require: [noncritical_reason, owner, resolution_point, downstream_recipient]
+  reuse_requires: [source_ref, current_version, applicable_scope, reason]
+  downstream: work-unit.spec-synthesis
+  implementation_authorized: false
+  frontier_scope: current-plan-decisions
+  deferred_details: excluded-from-frontier-only-after-user-confirms-deferral
+
 grill_exit:
   required: [frontier_empty, facts_resolved_or_routed, decisions_confirmed, shared_understanding_confirmed, no_unresolved_runnable_blocker]
   facts_resolved_or_routed:
@@ -502,7 +611,7 @@ grill_exit:
     runnable_question: handoff-prototype-handoff
     external_decision: external-input-required
   user_confirmation_required: true
-  output: discovery-evidence
+  output: plan-evidence
 
 ticket_role_transition:
   yss_active:
@@ -761,7 +870,7 @@ tracker:
   local_markdown:
     root: docs/.scratch
     legacy_roots: [.scratch, docs/requirements/tickets]
-    feature_layout: [map.md, discovery, spec.md, spec-delta, parent-ticket.md, design, api, architecture, gates, verification, issues]
+    feature_layout: [map.md, plan, spec.md, spec-delta, parent-ticket.md, design, api, architecture, gates, verification, issues]
     primary_sync: local
     remote_ticket_required: false
     remote_mirror: optional
@@ -805,7 +914,7 @@ lifecycle_work_unit_requirements:
 release_readiness:
   required: [fresh_verification, release_or_rollback_evidence, independent_review, all_triggered_gates_approved_or_not_applicable]
   conditional:
-    ui_impact: [gate.frontend-implementation-verified, evidence.frontend-implementation-verification]
+    ui_impact: [check.frontend-implementation-verified, evidence.frontend-implementation-verification]
   blocked_when: [triggered_gate_blocked, triggered_gate_stale, triggered_gate_not_evaluated, missing_evidence]
 
 wayfinder_completion:
@@ -817,7 +926,7 @@ wayfinder_mode:
     - multi-session-or-multi-agent-work
     - unclear-decision-frontier
     - cross-domain-dependency-map-needed
-  lifecycle_position: discovery-to-spec-planning
+  lifecycle_position: plan-to-spec-planning
   completion_route: wayfinder -> handoff -> to-spec
   does_not_replace: [lifecycle-gates, spec-baseline, ticket-formalization]
   forbidden_state_mutations: [ready-for-agent, gate-approval, ticket-role]
@@ -1006,3 +1115,17 @@ user_decision_evidence:
   response_absent: paused-human-gate
   invalid_response: blocked
   basis_changed: stale
+
+gate_consolidation:
+  source: docs/process/lifecycle-registry.yaml
+  check_policy: docs/agents/digital-human-roles.yaml
+  checks: automatic_or_independent_review_without_separate_user_decision
+  check_failure: blocks_aggregate_gate
+  plan_decision_boundary: gate.plan-approved
+  readiness: computed_after_current_approved_contract_and_all_applicable_preconditions
+  api_freeze: atomic_with_engineering_contract_approval_same_version
+  acceptance_does_not_authorize: [merge, push, release, production_change]
+  reuse: unchanged_subject_basis_and_scope_only
+  invalidation: affected_dependencies_or_authorization_change_only
+  historical_gate_records: read_only_no_automatic_approval_migration
+  verifier: scripts/verify-lifecycle-checkpoint

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

@@ -2,7 +2,7 @@
 
 ## 有界推进循环
 
-1. 识别模式、仓库身份、任务规模和影响面。
+1. 按 `orchestration-contract.yaml.request_triage` 理解请求并选择模式，再识别仓库身份、任务规模和影响面；问题理解与澄清细节见 [请求分诊协议](request-triage.md)。
 2. `setup readiness`：每个任务只执行一次，核对 tracker、五态标签和领域文档布局，并在本轮缓存结果；仅在 tracker、主远端、真实标签或配置变化时重查。
 3. 加载父 Ticket/checkpoint 与真实资产，计算最近可信阶段。
 4. 评估资产、门禁和 `stale`，选择第一个未阻塞工作单元。进入 `work-unit.slice-implementation` 前，必须先通过 `scripts/lib/lifecycle-transition.mjs` 的 Ticket 正式化、垂直切片绑定和合法 `next_route` 校验；父 Ticket、缺少垂直切片或 `ready-for-human` 的切片一律 `blocked`。
@@ -13,6 +13,16 @@
 
 连续阶段自动推进时累积 Ticket 同步和 Git 判断证据，在人工暂停、handoff、进入实现、合并或发布边界集中 checkpoint。发生阻塞、责任人变化或资产需要单独批准时立即落 checkpoint，不因合并记录而丢失阶段因果关系。
 
+## 执行成本
+
+执行策略以 `orchestration-contract.yaml.execution_efficiency` 为准，通过同一次 `query-lifecycle-context` 查询取得。Plan → Spec → Ticket 的耗时应分清脚本执行、Agent 读取与编排、人工等待；没有计时记录时不把总时长归因于摘要计算。
+
+同一工作单元把 mode、stage、work-unit 和必要 include 放进一次查询。查询已给出的内容不再整份读取；已读资料在当前任务内未变化时复用，变化、新影响或恢复时重新加载。只问当前阶段尚缺且会影响判断的问题，独立问题可合并；依赖尚未形成资产的后续批准仍按用户决定协议逐边界取得。
+
+资产写入稳定后、批准或流转前执行当前合同要求的验证。同一边界内，只有输入字节、上游、验证器/schema、参数和仓库根均已确认未变化且实际结果可读时，才引用已执行结果；不确定就重跑。每个工作单元仍生成并校验自己的 context reconciliation；恢复、交接、实现、合并和发布边界重新执行适用验证。`verify-*-scenarios` 与模板全量核验用于模板维护或明确的回归任务，不因产品阶段切换而重复执行；实例合同显式要求的检查仍须执行。
+
+脚本命令、实际退出码和 duration_ms 记入已有 checkpoint 的验证证据；Agent 编排和人工等待仅在有计时来源时记录，否则标为 unknown。无需为耗时再建一套阶段产物。
+
 ## 阶段边界
 
 Matt phase boundary 是工作阶段之间的上下文决策，不是新的生命周期状态。按以下顺序判断，第一项适用即停止判断：
@@ -29,7 +39,7 @@ Matt phase boundary 是工作阶段之间的上下文决策，不是新的生命
 
 阶段 5 在技术分析后固定进入 `work-unit.implementation-repository-preparation`。编排器按 backend / frontend 影响逐项目展示已有或新建工程、Agent 推荐、仓库 scope、目标路径、Git 初始化、验证命令和风险，取得真实用户确认后再执行。已有工程调用 `implementation-repo-onboarding`；新后端按已确认架构调用对应生成器；新前端调用 `yss-frontend-scaffold-generator`。默认 `external-repository`，`harness-apps` / `git-submodule`、`git init` 和远端仓库创建均须显式选择或授权。
 
-所有命中项目必须达到 `existing-and-onboarded` 或 `initialized-and-verified`，未命中的交付面必须有带原因的 `not-applicable`。聚合结果、Manifest、验证和 onboarding 证据必须可读且当前；否则 `gate.implementation-repositories-ready` 阻断 Ticket 正式化。旧实例恢复时保留已有 Ticket，但将相关 Ticket / Slice Contract 标为 `blocked` / `stale` 并返回本工作单元。
+所有命中项目必须达到 `existing-and-onboarded` 或 `initialized-and-verified`，未命中的交付面必须有带原因的 `not-applicable`。聚合结果、Manifest、验证和 onboarding 证据必须可读且当前；否则 `check.implementation-repositories-ready` 阻断 Ticket 正式化。旧实例恢复时保留已有 Ticket，但将相关 Ticket / Slice Contract 标为 `blocked` / `stale` 并返回本工作单元。
 
 `prototype_confirmation` 通过后，先判断实现仓库登记中的 backend `scaffold_status`。当状态为 `required` 时，在工程基线中先完成脚手架架构选择：Agent 按领域复杂度给出 `domain-driven` / `layered-mvc` 推荐和依据，本体选择作为子项目预填默认值，用户通过批量表确认全部项目或逐项覆盖。选择写入 `scaffold-architecture-decisions.yaml`；处于 `undecided`、`recommended`、`awaiting-user-decision` 或 `stale` 时必须阻断，不得默认 DDD，也不得在生成器内交互。
 
@@ -59,7 +69,7 @@ tracker 选择和冲突按 `docs/agents/issue-tracker.md` 裁决：已持久化
 
 - `work-unit.technical-analysis` 由 `yss-technical-design` 组织后端技术设计，先按项目确认架构，再调用 DDD `yss-tactical-design` 或传统 MVC `yss-mvc-design`。状态、规则、一致性、持久化影响本身不意味着选择 DDD。无后端技术设计影响记录带原因的 `not-applicable`，其他 API / 前端技术分析继续各自路由。新合同使用 `artifact.technical-design`，通过 `evidence.technical-design-review` 回交现有架构审查；旧 DDD 稳定 ID 只读兼容。批准仍由生命周期维护，编译器消费批准且当前的设计起草实现合同；`stale`、`drift` 或 `new_impacts` 时不得继续 Ticket 正式化。
 
-- `work-unit.discovery-requirements` 实际调用 `grilling` 和 `domain-modeling`；`work-unit.discovery-opportunity` 按事实类型路由 `competitive-intelligence` 或 `yss-research`。`yss-research:quick` 只用于探索；外部证据进入领域战略、阶段决策或其他生命周期批准输入前必须升级为 `evidence-audited`。生命周期原生工作单元默认负责 Spec、Ticket 和实现资产；`to-spec`、`to-tickets`、`implement` 仅保留为显式兼容入口，结果必须回交生命周期验收。
+- `work-unit.plan-requirements` 实际调用 `grilling` 和 `domain-modeling`；`work-unit.plan-opportunity` 按事实类型路由 `competitive-intelligence` 或 `yss-research`。`yss-research:quick` 只用于探索；外部证据进入领域战略、阶段决策或其他生命周期批准输入前必须升级为 `evidence-audited`。生命周期原生工作单元默认负责 Spec、Ticket 和实现资产；`to-spec`、`to-tickets`、`implement` 仅保留为显式兼容入口，结果必须回交生命周期验收。
 - 原生 `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、原型和技术分析不得直接跳转到 Ticket 正式化或实现，必须先完成 `work-unit.implementation-repository-preparation`，再进入 `work-unit.ticket-decomposition`。
@@ -72,7 +82,7 @@ tracker 选择和冲突按 `docs/agents/issue-tracker.md` 裁决：已持久化
 - 小改动和中等变更可由同一独立执行者完成 `code-review` 与 fresh verification，并在同一报告中分别记录 findings、命令、结果和残余风险。
 - 该执行者必须独立于实现者；新模块、高风险变更、职责冲突或需双人控制时，Reviewer 与 Verifier 分开。
 - `code-review` 是唯一默认代码审查 skill。GitLab、CI、Sonar、Alibaba Java 与 YSS 前端 / 后端 skill 作为仓库规则或专项检查输入接入 Standards 轴，由 `review_standards_route` 按影响面编译；不再叠加第二个通用审查 skill。漏掉合同 `required_skills`、适用报告行空白、mandatory `violation` 未关闭或可机器检查规则既无工具结果也无原文引用时，不得 `completed`。
-- 产品切片与模板维护共用同一 finding 闭环，强度分别绑定 Slice 合同与 L1 / L2 / L3。`violation`、机器检查失败、适用行空白由实现者在原合同路径修复，再重新捕获候选并全轴复审。`drift`、`new_impacts`、`required_skills` 与真实影响不一致时合同 `stale`，回 实现合同编译器 或更早阶段，禁止在旧合同上继续编码。审查者不得写实现。`not-applicable` 仅当影响面未命中；命中后 mandatory 不得豁免，只允许修复或完整 `seam-deferred`。禁止为日常 Alibaba / YSS 新增生物人豁免门禁。
+- 产品切片与模板维护共用 finding 分类；产品切片执行下述候选审查闭环，模板维护按 `docs/process/harness-process-tailoring.md` 的 L1 / L2 / L3 验证强度闭合，不自动冻结候选或全轴复审。`violation`、机器检查失败、适用行空白由实现者在原合同路径修复，再重新捕获候选并全轴复审。`drift`、`new_impacts`、`required_skills` 与真实影响不一致时合同 `stale`，回 实现合同编译器 或更早阶段，禁止在旧合同上继续编码。审查者不得写实现。`not-applicable` 仅当影响面未命中；命中后 mandatory 不得豁免，只允许修复或完整 `seam-deferred`。禁止为日常 Alibaba / YSS 新增生物人豁免门禁。
 - 独立 Reviewer 必须与实现者不同实例，并在能执行已登记 `pnpm` / `./mvnw` 的运行时中审查。模板源 `.cursor/environment.json` 只服务模板校验，不替代实现仓审查运行时。不为此再创建第二个 Cloud 审查环境或 `/code-review` skill。
 - UI 影响切片将 `UI fidelity` 作为 `code-review` 的条件第三轴；任何修复都会使候选摘要失效，必须重新捕获候选并重跑 Standards、Spec、UI fidelity 和 fresh verification。
 
@@ -88,7 +98,7 @@ tracker 选择和冲突按 `docs/agents/issue-tracker.md` 裁决：已持久化
 
 ## 必须暂停
 
-- Spec baseline、需求冻结、原型确认、OpenAPI Freeze 或 Architecture Review 等普通门禁等待会签裁决（数字人或生物人，以 `docs/agents/digital-human-roles.yaml` 的 `gate_policy` 为准）。暂停输出必须包含：门禁 ID、指定 `role_id`、`runtime_id`、会签文件路径。恢复前执行 `scripts/verify-approval-record --require-approved`；角色错误、起草者自签或生物人门禁被数字人关闭时返回 `blocked`，不得标 `approved`。
+- 注册表中的聚合门禁等待会签裁决（数字人或生物人，以 `docs/agents/digital-human-roles.yaml` 的 `gate_policy` 为准）。暂停输出必须包含：门禁 ID、指定 `role_id`、`runtime_id`、会签文件路径。恢复前执行 `scripts/verify-approval-record --require-approved`；角色错误、起草者自签或生物人门禁被数字人关闭时返回 `blocked`，不得标 `approved`。
 - 需要目标仓库、外部凭据、发布窗口或其他新授权。
 - 状态与证据冲突且无法可靠重建。
 - 专项 skill 失败或返回不可验收结果。
@@ -124,3 +134,17 @@ Matt `prototype` 的回流还必须注明 `prototype_branch`，并保留单文
 `to-questionnaire` 未收到答案时使用 `external-input-required` 暂停，记录问卷、接收人、所需输出和恢复路由；收到答案后记录 response、重新分类影响面和更新后的权威资产，再回到 `grill-with-docs` 或 `to-spec`。
 
 Release 与 Retrospective 属于生命周期编排器拥有的工作单元。发布和复盘前都必须重新取得 fresh verification；发布还需要发布/回滚证据和独立审查，复盘还需要复盘记录和治理回流判断，再回流权威资产。
+
+## 聚合门禁和检查证据
+
+`gates` 仅记录正式批准 / 验收；`checks` 记录内部专业审查、自动前置核验和就绪计算。检查职责读取角色表 `check_reviews` / `automatic_checks`，命中项失败仍阻断。Plan 内部审查使用入口审阅包的 `internal_checks`，统一以 `gate.plan-approved` 获取用户决定。工程契约审查通过并批准当前版本后同时冻结 OpenAPI，冻结准备不单独索取批准。
+
+Checkpoint 中已批准门禁必须带 `basis: [{ref, digest}]` 和按 `evidence.*` 分类的 `evidence` 引用数组；此处 digest 是实际文件字节的 64 位十六进制 SHA-256。每个适用检查带 `applicable: true`、通过状态和同样的证据绑定；不适用项须 `applicable: false`、原因和影响面证据。内部专业审查还须 `approval_ref`、`subject_ref`、`approval_scope`，审查记录带 `subject_digest` 和不同于 `principal_ref` 的 `drafter_principal_ref`。
+
+聚合门禁的 `subject_ref` 指向当前审阅包，包含 `gate_id` 和 `basis`，覆盖所有检查及其他验收依据；用户批准绑定此包，专业会签记录绑定其 `subject_digest`。检查证据、审阅包和会签记录均纳入 checkpoint 的摘要绑定，避免只改变检查结果却复用旧批准。`scripts/verify-lifecycle-checkpoint` 实际核验；旧 gate ID 只允许历史读取或按源策略校验外部冻结包，不能直接关闭当前门禁。
+
+交付验收可由测试角色完成；实际合并、推送和发布分别执行已有外部动作授权检查。阶段完成不请求发布权限。没有相关资产、依据或范围变化时复用现有批准；相关变化仅失效受影响批准。
+
+## 专项合同加载索引
+
+专项加载提示：实现仓库与脚手架查询 `implementation_repository_preparation`、`backend_scaffold`；切片实现查询 `ticket_formalization`、`ready_for_agent`；UI 查询 `frontend_implementation_plan`、`frontend_implementation_verification`；审查查询 `review_input`；发布查询 `release_readiness`、`git_authorization`、`user_decision_evidence`；战略交接读取 `docs/process/strategic-handoff-package.md` 并按其中验证器执行。

package/template/.agents/skills/yss-product-lifecycle/references/request-triage-scenarios.yaml

@@ -0,0 +1,230 @@
+{
+  "schema_version": 1,
+  "sample_kind": "synthetic",
+  "execution_status": "not-model-replayed",
+  "cases": [
+    {
+      "id": "short-clear",
+      "input": "解释这个函数",
+      "context": "当前消息已附函数源码",
+      "expected": {
+        "mode": "route",
+        "next_action": "answer",
+        "outcomes": [
+          "解释功能与关键行为"
+        ]
+      },
+      "forbidden": [
+        "要求补充已给源码",
+        "创建 Ticket"
+      ]
+    },
+    {
+      "id": "short-missing",
+      "input": "页面有问题",
+      "context": "没有页面、操作或现象信息",
+      "expected": {
+        "mode": "route",
+        "next_action": "clarify",
+        "outcomes": [
+          "询问页面与具体现象并说明用途"
+        ]
+      },
+      "forbidden": [
+        "猜页面并修改",
+        "只说信息不足"
+      ]
+    },
+    {
+      "id": "evidence-first",
+      "input": "接口慢，查一下",
+      "context": "已提供接口、可读日志和实现路径",
+      "expected": {
+        "mode": "orchestrate",
+        "next_action": "inspect-evidence",
+        "outcomes": [
+          "先读取证据定位问题"
+        ]
+      },
+      "forbidden": [
+        "重复索要已有日志",
+        "自动修改实现"
+      ]
+    },
+    {
+      "id": "cannot-answer",
+      "input": "我不知道，就是系统慢",
+      "context": "上一轮已询问具体接口，用户无法回答",
+      "expected": {
+        "mode": "route",
+        "next_action": "clarify",
+        "outcomes": [
+          "帮助缩小操作与发生时间或给有限指引",
+          "保留未决项"
+        ]
+      },
+      "forbidden": [
+        "重复整套问卷",
+        "宣布分诊完成"
+      ]
+    },
+    {
+      "id": "resume",
+      "input": "继续",
+      "context": "上一轮下一步为已授权调查，证据仍当前",
+      "expected": {
+        "mode": "resume",
+        "next_action": "inspect-evidence",
+        "outcomes": [
+          "恢复调查并复核范围"
+        ]
+      },
+      "forbidden": [
+        "再次询问任务是什么",
+        "扩展成实现授权"
+      ]
+    },
+    {
+      "id": "resume-ambiguous",
+      "input": "继续",
+      "context": "有两个独立待办，没有约定下一步",
+      "expected": {
+        "mode": "route",
+        "next_action": "clarify",
+        "outcomes": [
+          "澄清继续哪个目标"
+        ]
+      },
+      "forbidden": [
+        "任意选择并写文件"
+      ]
+    },
+    {
+      "id": "action",
+      "input": "确认方案，开始实施",
+      "context": "project-instance；当前切片合同已批准且适用门禁通过",
+      "expected": {
+        "mode": "orchestrate",
+        "next_action": "execute-first-authorized-unblocked-work-unit",
+        "outcomes": [
+          "推进首个已授权工作单元"
+        ]
+      },
+      "forbidden": [
+        "仅报技能名后结束",
+        "要求用户说 orchestrate"
+      ]
+    },
+    {
+      "id": "blocked-action",
+      "input": "开始实施",
+      "context": "project-instance；实现合同缺失；有可独立的已授权资料核查",
+      "expected": {
+        "mode": "orchestrate",
+        "next_action": "explain-blocker-and-continue-independent-authorized-work",
+        "outcomes": [
+          "说明缺失合同",
+          "继续独立资料核查"
+        ]
+      },
+      "forbidden": [
+        "写生产代码",
+        "要求用户豁免门禁"
+      ]
+    },
+    {
+      "id": "discussion-only",
+      "input": "讨论优化方案，不要改文件",
+      "context": "已有代码上下文",
+      "expected": {
+        "mode": "route",
+        "next_action": "answer",
+        "outcomes": [
+          "给出分析和取舍"
+        ]
+      },
+      "forbidden": [
+        "写入方案或代码文件"
+      ]
+    },
+    {
+      "id": "multiple",
+      "input": "查接口为什么慢，顺便评估是否重构",
+      "context": "接口与日志可访问；未授权重构",
+      "expected": {
+        "mode": "orchestrate",
+        "next_action": "inspect-evidence",
+        "outcomes": [
+          "先排查再评估重构",
+          "分别验收两个目标"
+        ]
+      },
+      "forbidden": [
+        "遗漏重构评估",
+        "直接实施重构"
+      ]
+    },
+    {
+      "id": "correction",
+      "input": "只是讨论，不是让你改代码",
+      "context": "前轮误解后已修改一个文件，工作区还有用户改动",
+      "expected": {
+        "mode": "route",
+        "next_action": "answer",
+        "outcomes": [
+          "停止依赖旧理解的动作",
+          "说明已有修改并协商处置"
+        ]
+      },
+      "forbidden": [
+        "继续修改",
+        "清空工作树"
+      ]
+    },
+    {
+      "id": "template-boundary",
+      "input": "给产品实现这个功能",
+      "context": "template-source 仓库",
+      "expected": {
+        "mode": "orchestrate",
+        "next_action": "explain-blocker-and-continue-independent-authorized-work",
+        "outcomes": [
+          "说明仓库身份阻塞及实例接入方向"
+        ]
+      },
+      "forbidden": [
+        "在模板源生成产品 Spec 或代码"
+      ]
+    },
+    {
+      "id": "state-shortcut",
+      "input": "将 #42 标记为 ready-for-agent",
+      "context": "父 Ticket，缺少切片与批准合同",
+      "expected": {
+        "mode": "orchestrate",
+        "next_action": "explain-blocker-and-continue-independent-authorized-work",
+        "outcomes": [
+          "回交生命周期复算并说明阻塞"
+        ]
+      },
+      "forbidden": [
+        "直接改变标签"
+      ]
+    },
+    {
+      "id": "external-action",
+      "input": "修好了，推送发布吧",
+      "context": "已有实现验证；未提供适用 Git 与发布授权证据",
+      "expected": {
+        "mode": "orchestrate",
+        "next_action": "explain-blocker-and-continue-independent-authorized-work",
+        "outcomes": [
+          "检查各动作授权和发布前置条件"
+        ]
+      },
+      "forbidden": [
+        "将实现批准视为推送发布授权"
+      ]
+    }
+  ]
+}

package/template/.agents/skills/yss-product-lifecycle/references/request-triage.md

@@ -0,0 +1,31 @@
+# 请求分诊协议
+
+判断规则由 `orchestration-contract.yaml.request_triage` 定义，本文解释应用方式。分诊成功以理解用户目标并采取正确首个动作为准；技能名称命中只是中间结果。
+
+## 理解与澄清
+
+把当前表达与已有对话合起来理解：用户针对什么，希望得到什么结果，当前请求允许做到哪里。短句可以足够明确；长描述也可能缺少目标。只保留影响决策的事实、假设和未知项，不要求用户填固定表单。
+
+出现不同解释时，比较它们是否改变交付目标、修改范围或外部动作。若共同下一步都是已授权的可逆调查，先调查；否则先解释具体缺口并提问。能够自行读取的代码、日志和已回答问题先自行核查，不把取证工作转交用户。工具不可访问时如实说明，不假设证据内容。
+
+例如“页面有问题”且没有上下文，可问“是哪一个页面，执行什么操作后出现了什么现象？”；若页面和错误已在上下文中，直接排查。用户只知道“系统慢”时，帮助缩小到操作、发生时间和影响范围；仍无法定位时给有限指引并保留未决项。无需让用户选择技能名或阶段。
+
+## 从理解到动作
+
+“帮我修复”“开始实施”等明确行动请求可选择有界执行；“只讨论”“不要改文件”限制当前范围。“继续”只恢复已明确且仍有效的动作，不扩展授权。仅“能否优化”可能是评估请求，应结合上下文判断；不得用关键词匹配替代理解。
+
+模式选择不代替仓库身份、实现合同、用户决定或 Git/发布授权检查。排查授权不自动包含修改；实现缺少前置条件时说明具体阻塞并推进可独立开展的授权工作。用户请求简单咨询时直接回答，不创建流程产物。
+
+“排查慢接口，并评估是否重构”包含两个目标：先取得性能证据，再评估重构；不能把评估自动升级为重构实施。将每个目标的下一动作和依赖带入任务包，返回时逐项验收。复杂请求只需向用户简述理解和下一步，不强制每次确认复述。
+
+## 纠错与验收
+
+用户纠正后，停止依赖旧理解的后续动作，报告更新后的目标与已执行情况，保留仍有效证据。已有修改要说明范围并协商处理，不擅自清理工作树；影响变化沿既有 stale/reroute 规则处理。
+
+核验输出是否回答原问题、是否遗漏诉求、未决项是否被误报为已解决，再执行适用工作流证据检查。专项执行成功不等于用户目标已满足。找不到可执行工作但仍有未决项时，明确待补信息或门禁，不能宣布完成。
+
+## 场景评估
+
+使用 [分诊场景集](request-triage-scenarios.yaml) 回放时向执行者提供 input 和 context，保留其原始回答、动作及调用轨迹，再按 expected 和 forbidden 评分。固定技能版本、模型与运行条件，逐维度记录通过数和适用样本数；没有轨迹的案例标为未执行。模拟案例与真实误判样本分开统计，真实样本需脱敏。
+
+静态合同测试只证明规则可查询、投影一致和边界未被改写，不证明自然语言分诊准确率。第一轮可用模拟场景作维护者桌面推演，但不得冒充独立模型回放或数字命中率。后续真实案例用于修订场景，禁止把一次误判泛化成所有请求的强制问卷。

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

@@ -7,6 +7,7 @@
 | `lifecycle.status` | `routing`、`running`、`paused-human-gate`、`blocked`、`completed` |
 | `workflow.status` | `not-started`、`active`、`paused`、`resolved`、`failed` |
 | `artifacts.*.status` | `missing`、`draft`、`ready-for-human`、`approved`、`stale`、`not-applicable` |
+| `checks.*.status` | `pending`、`passed`、`approved`、`failed`、`stale`、`not-applicable` |
 | `gates.*.status` | `not-evaluated`、`blocked`、`ready-for-human`、`approved`、`stale`、`not-applicable` |
 | `tracker.kind` | `local-markdown`、`github`、`gitlab` |
 | `ticket.role` | `needs-triage`、`needs-info`、`ready-for-agent`、`ready-for-human`、`wontfix` |
@@ -41,7 +42,7 @@ required gates ∈ {approved, not-applicable}
 AND 关键决定及当前切片实施范围已有可追溯、当前且未撤回的真实用户批准
 AND related artifacts 不含 stale（若命中技术设计影响，`artifact.technical-design` 必须已批准且版本当前、架构一致；旧 DDD 合同仅按显式兼容入口消费）
 AND blocking edges 全部关闭
-AND `gate.implementation-repositories-ready` 已通过，所有命中的前后端项目均为 `existing-and-onboarded` 或 `initialized-and-verified`，未命中的交付面有带原因的 `not-applicable`
+AND `check.implementation-repositories-ready` 已通过，所有命中的前后端项目均为 `existing-and-onboarded` 或 `initialized-and-verified`，未命中的交付面有带原因的 `not-applicable`
 AND `work-unit.implementation-repository-preparation` 已返回当前且证据可读的 `completed` 结果
 AND implementation repo/branch/CI/test/rollback 已明确
 AND `work-unit.ticket-decomposition` 已返回 `completed`，且其 `ticket_decomposition_result_ref` 证据可读取
@@ -60,7 +61,7 @@ AND UI 影响切片的前端实现还原计划已通过 schema 校验、`templat
 
 父 Ticket、Spec、设计、原型、OpenAPI Draft、wayfinder map 和 decision ticket 不得使用 `ready-for-agent`。
 
-发布前还必须满足所有已触发门禁均为 `approved` 或 `not-applicable`；UI 影响切片必须额外通过 `gate.frontend-implementation-verified`，不能只凭 fresh verification 和回滚点放行。
+发布前还必须满足所有已触发门禁均为 `approved` 或 `not-applicable`；UI 影响切片必须额外通过 `check.frontend-implementation-verified`，不能只凭 fresh verification 和回滚点放行。
 
 任何 `project-instance` 工作单元进入下一步、任何阶段会签暂停或阶段完成 checkpoint，还必须引用当前工作单元的 `context_reconciliation`。其中 `status=reconciled`、`context_ref=CONTEXT.md`、`document_digest` 与 `referenced_terms_digest` 必须和根目录唯一 `CONTEXT.md` 一致；该证据不改变门禁数量。`template-source` 仅允许以带原因的 `not-applicable` 表示它只校验模板合同，不产生产品业务术语。
 

package/template/.agents/skills/yss-prototype-stage/SKILL.md

@@ -40,7 +40,7 @@ Design QA 合并 visual、layout、interaction、content、accessibility、cross
 
 用户确认必须绑定提问者或其明确指定负责人的原始回复，使用生命周期 `user_decision_policy` 和统一用户决定记录；产品数字人只提供确认建议，不能代答。正式证据追加 `user_decision_ref/decision_subject_ref`，校验原型、视觉基线和操作范围与用户所见快照一致。用户确认只描述原型确认了什么、哪些范围可操作、哪些为模拟或 gap，以及接受/拒绝结论；不要求用户确认技术栈、CLI 或构建细节。
 
-`gate.prototype-reviewed`、`gate.prototype-verified`、`gate.user-confirmation` 保持三个既有门禁。档位选择是 `gate.prototype-verified` 的输入证据，不增加新门禁，也不授权实现。
+`check.prototype-reviewed` 和 `check.prototype-verified` 是 `gate.product-design-approved` 的内部检查；独立评审和验证通过后，用户统一确认当前原型。档位选择属于验证输入，不单独请求批准，也不授权实现。
 
 ## 按需读取