create-yss-spec 3.3.4 → 3.3.7

package/template/.agents/skills/yss-stage-decision/tests/fixtures/valid-stage-decision-package.yaml

@@ -1,16 +1,41 @@
-schema_version: 2
+schema_version: 3
 stage_decision_id: stage-decision.supplier-admission
-package_version: v2
+package_version: v3
 status: approved
 problem_statement: 合规准入决定分散，采购无法稳定判断当前有效资格。
 target_users: [采购专员、合规专员]
 mvp: [提交供应商申请、合规准入决定、采购侧有效性校验]
 non_goals: [供应商结算、采购付款、通用工作流平台]
-success_criteria: [新采购订单 100% 校验当前有效准入决定]
-test_seams: [supplier-application-submit, admission-validity-check]
-confirmed_decisions: [ComplianceReview 拥有准入规则语义，ProcurementExecution 只消费决定]
-assumptions: [供应商已有唯一 subject_ref]
-constraints: [保留现有采购订单流程]
+success_criteria:
+  - id: success-criterion.current-admission
+    statement: 新采购订单 100% 校验当前有效准入决定。
+    source_refs: [rule.current-admission-required]
+    evidence_refs: [evidence.discovery.compliance]
+    status: confirmed
+test_seams:
+  - id: test-seam.admission-validity-check
+    statement: admission-validity-check
+    source_refs: [scenario.admission-expires, invariant.current-admission-required]
+    evidence_refs: [evidence.discovery.compliance]
+    status: confirmed
+confirmed_decisions:
+  - id: decision.compliance-owns-admission-rules
+    statement: ComplianceReview 拥有准入规则语义，ProcurementExecution 只消费决定。
+    source_refs: [rule.current-admission-required]
+    evidence_refs: [evidence.domain-strategy-review.supplier]
+    status: confirmed
+assumptions:
+  - id: assumption.unique-subject-ref
+    statement: 供应商已有唯一 subject_ref。
+    source_refs: [scenario.supplier-submits]
+    evidence_refs: [evidence.discovery.supplier]
+    status: confirmed
+constraints:
+  - id: constraint.preserve-procurement-flow
+    statement: 保留现有采购订单流程。
+    source_refs: [scenario.admission-expires]
+    evidence_refs: [evidence.discovery.compliance]
+    status: confirmed
 unresolved_items:
   - item: 供应商历史资料迁移范围
     type: deferred
@@ -25,7 +50,7 @@ context_snapshot:
   term_refs: [Global/Supplier, ComplianceReview/AdmissionDecision]
 domain_strategy_ref:
   domain_strategy_id: domain-strategy.supplier-admission
-  domain_version: v2
+  domain_version: v3
   digest: <domain-strategy-digest>
   status: approved
   persisted_ref: domain-strategy.yaml
@@ -38,17 +63,21 @@ impact_assessment:
   cross_repo: false
   high_risk: false
 downstream_mapping:
-  - domain_change: admission-decision-validity
-    consumer: spec-synthesis
+  - mapping_id: mapping.backend-admission-validity
+    source_refs: [rule.current-admission-required, invariant.current-admission-required]
+    consumer_capability: backend-technical-design
     propagation: direct
     reapproval_condition: 领域策略版本或有效性规则变化
-  - domain_change: admission-decision-validity
-    consumer: ticket-decomposition
+    evidence_refs: [evidence.domain-strategy-review.supplier]
+  - mapping_id: mapping.frontend-admission-validity
+    source_refs: [scenario.admission-expires]
+    consumer_capability: frontend-engineering-design
     propagation: transitive
     reapproval_condition: Spec 基线变更
+    evidence_refs: [evidence.domain-strategy-review.supplier]
 evidence_refs: [evidence.discovery.supplier, evidence.domain-strategy-review.supplier]
 approval:
   approval_ref: .agents/skills/yss-stage-decision/tests/fixtures/stage-decision-approval.yaml
   approver: role.product-manager
   persisted_ref: docs/.scratch/supplier/stage-decision/stage-decision-package-v1.yaml
-  current_version: v2
+  current_version: v3

package/template/.agents/skills/yss-stage-decision/tests/fixtures/valid-supplier-domain.yaml

@@ -1,7 +1,19 @@
-schema_version: 2
+schema_version: 3
 domain_strategy_id: domain-strategy.supplier-admission
-domain_version: v2
+domain_version: v3
 status: approved
+traceability_version: 1
+rule_catalog:
+  - rule_id: rule.application-material-complete
+    statement: 申请材料必须完整
+    responsible_context: SupplierManagement
+    status: confirmed
+    evidence_refs: [evidence.discovery.supplier]
+  - rule_id: rule.current-admission-required
+    statement: 新采购订单必须引用当前有效的准入决定。
+    responsible_context: ComplianceReview
+    status: confirmed
+    evidence_refs: [evidence.discovery.compliance]
 contexts:
   - context_id: SupplierManagement
     name: 供应商管理
@@ -64,6 +76,10 @@ scenarios:
     preconditions: [供应商资料可编辑]
     commands: [SubmitSupplierApplication]
     rules: [申请材料必须完整]
+    rule_refs: [rule.application-material-complete]
+    critical: true
+    success_results: [完整申请进入合规审查]
+    evidence_refs: [evidence.discovery.supplier]
     events: [SupplierApplicationSubmitted]
     failure_results: [材料不完整时拒绝提交]
     responsible_context: SupplierManagement
@@ -73,7 +89,11 @@ scenarios:
     actor: compliance-officer
     preconditions: [批准决定存在]
     commands: [EvaluateAdmissionValidity]
-    rules: [过期决定不得支持新采购订单]
+    rules: [新采购订单必须引用当前有效的准入决定。]
+    rule_refs: [rule.current-admission-required]
+    critical: true
+    success_results: [过期准入决定不能支持新采购订单]
+    evidence_refs: [evidence.discovery.compliance]
     events: [SupplierAdmissionExpired]
     failure_results: [采购下单时资格校验失败]
     responsible_context: ComplianceReview
@@ -94,6 +114,8 @@ invariants:
     responsible_context: ComplianceReview
     scenario_refs: [scenario.admission-expires]
     verification_method: 领域场景测试和事件版本校验
+    rule_ref: rule.current-admission-required
+    evidence_refs: [evidence.discovery.compliance]
 context_snapshot:
   context_ref: CONTEXT.md
   context_schema_version: 1
@@ -101,13 +123,23 @@ context_snapshot:
   referenced_terms_digest: <referenced-terms-digest>
   term_refs: [Global/Supplier, ComplianceReview/AdmissionDecision]
 downstream_mapping:
-  - domain_change: admission-decision-validity
+  - mapping_id: mapping.backend-admission-validity
+    source_refs: [rule.current-admission-required, invariant.current-admission-required]
+    consumer_capability: backend-technical-design
     impacts: [spec, openapi, procurement-acceptance-tests]
     propagation: stale
     reapproval_condition: ComplianceReview 决定和有效期重新批准
+    evidence_refs: [evidence.discovery.compliance]
+  - mapping_id: mapping.frontend-admission-validity
+    source_refs: [scenario.admission-expires]
+    consumer_capability: frontend-engineering-design
+    impacts: [ui, frontend]
+    propagation: direct
+    reapproval_condition: 场景结果或视觉基线变化
+    evidence_refs: [evidence.discovery.compliance]
 evidence_refs: [evidence.discovery.supplier, evidence.discovery.compliance]
 approval:
   approval_ref: .agents/skills/yss-stage-decision/tests/fixtures/domain-strategy-approval.yaml
   approver: role.product-manager
   persisted_ref: docs/.scratch/supplier/domain/domain-strategy-v1.yaml
-  current_version: v2
+  current_version: v3

package/template/.agents/skills/yss-stage-decision/tests/run-scenarios.mjs

@@ -1,5 +1,4 @@
 #!/usr/bin/env node
-import { buildDecisionFixture } from "../../../../scripts/fixtures/user-decision/build-fixture.mjs";
 import { createHash } from "node:crypto";
 import { spawnSync } from "node:child_process";
 import { mkdtemp, readFile, rm, writeFile } from "node:fs/promises";
@@ -14,6 +13,7 @@ const validator = join(testsRoot, "..", "scripts", "validate-domain-strategy.mjs
 const packageValidator = join(testsRoot, "..", "scripts", "validate-stage-decision-package.mjs");
 const contextValidator = join(projectRoot, "scripts", "verify-context-contract");
 const migrationTool = join(testsRoot, "..", "scripts", "migrate-context-references.mjs");
+const v3MigrationTool = join(testsRoot, "..", "scripts", "migrate-contract-v3.mjs");
 const validTemplate = join(testsRoot, "fixtures", "valid-supplier-domain.yaml");
 const validPackageTemplate = join(testsRoot, "fixtures", "valid-stage-decision-package.yaml");
 
@@ -29,6 +29,58 @@ function digestYaml(source) {
   return `sha256:${createHash("sha256").update(JSON.stringify(canonical(document.toJS({ maxAliasCount: 0 })))).digest("hex")}`;
 }
 
+function parseYaml(source) {
+  const document = parseDocument(source, { maxAliasCount: 0, uniqueKeys: true });
+  if (document.errors.length) throw new Error(document.errors[0].message);
+  return document.toJS({ maxAliasCount: 0 });
+}
+
+function toV2Domain(source) {
+  const value = structuredClone(parseYaml(source));
+  value.schema_version = 2;
+  value.domain_version = "v2";
+  delete value.traceability_version;
+  delete value.rule_catalog;
+  for (const scenario of value.scenarios) {
+    delete scenario.rule_refs;
+    delete scenario.critical;
+    delete scenario.success_results;
+    delete scenario.evidence_refs;
+  }
+  for (const invariant of value.invariants) {
+    delete invariant.rule_ref;
+    delete invariant.evidence_refs;
+  }
+  value.downstream_mapping = [{
+    domain_change: "admission-decision-validity",
+    impacts: ["spec", "openapi", "procurement-acceptance-tests"],
+    propagation: "stale",
+    reapproval_condition: "ComplianceReview 决定和有效期重新批准"
+  }];
+  value.approval.current_version = "v2";
+  return value;
+}
+
+function toV2Stage(source, domainDigest) {
+  const value = structuredClone(parseYaml(source));
+  value.schema_version = 2;
+  value.package_version = "v2";
+  for (const field of ["success_criteria", "test_seams", "confirmed_decisions", "assumptions", "constraints"]) {
+    value[field] = value[field].map((item) => item.statement);
+  }
+  value.domain_strategy_ref.domain_version = "v2";
+  value.domain_strategy_ref.digest = domainDigest;
+  value.domain_strategy_ref.persisted_ref = "domain-strategy-v2.yaml";
+  value.downstream_mapping = [{
+    domain_change: "admission-decision-validity",
+    consumer: "spec-synthesis",
+    propagation: "direct",
+    reapproval_condition: "领域策略版本或有效性规则变化"
+  }];
+  value.approval.current_version = "v2";
+  return value;
+}
+
 function run(command, file, contextRoot) {
   return spawnSync(process.execPath, [command, file, "--root", contextRoot], { cwd: projectRoot, encoding: "utf8" });
 }
@@ -56,34 +108,59 @@ context_schema_version: 1
 | 准入决定 | 合规审查形成的准入结论。 | AdmissionDecision | ComplianceReview | 避免：\`审批结果\` |
 `;
 
-const temporaryRoot = await mkdtemp(join(tmpdir(), "yss-stage-decision-v2-"));
+const temporaryRoot = await mkdtemp(join(tmpdir(), "yss-stage-decision-v3-"));
 try {
   await writeFile(join(temporaryRoot, "CONTEXT.md"), contextSource);
   const contextResult = spawnSync(process.execPath, [contextValidator, "--root", temporaryRoot, "--allowed-context", "SupplierManagement", "--allowed-context", "ComplianceReview", "--allowed-context", "ProcurementExecution", "--term-ref", "Global/Supplier", "--term-ref", "ComplianceReview/AdmissionDecision", "--json"], { cwd: projectRoot, encoding: "utf8" });
   if (contextResult.status !== 0) throw new Error(`context fixture should pass: ${contextResult.stderr}`);
   const context = JSON.parse(contextResult.stdout);
 
-  const domainApprovalRef = join(temporaryRoot, "domain-approval.json");
   const domainSource = (await readFile(validTemplate, "utf8"))
-    .replace(".agents/skills/yss-stage-decision/tests/fixtures/domain-strategy-approval.yaml", domainApprovalRef)
     .replace("<document-digest>", context.document_digest)
     .replace("<referenced-terms-digest>", context.referenced_terms_digest);
   const domainFile = join(temporaryRoot, "domain-strategy.yaml");
   await writeFile(domainFile, domainSource);
-  const domainDecision = buildDecisionFixture(join(temporaryRoot, "domain-decision"), { boundary: "check.domain-strategy-approved", subjectRef: domainFile });
-  const domainApproval = parseDocument(await readFile(join(testsRoot, "fixtures/domain-strategy-approval.yaml"), "utf8")).toJS();
-  await writeFile(domainApprovalRef, JSON.stringify({ ...domainApproval, subject_ref: domainFile, approval_scope: domainDecision.requirement.scope, user_decision_ref: domainDecision.ref }));
   const pass = run(validator, domainFile, temporaryRoot);
-  if (pass.status !== 0) throw new Error(`valid v2 fixture should pass: ${pass.stderr}`);
+  if (pass.status !== 0) throw new Error(`valid v3 fixture should pass: ${pass.stderr}`);
+
+  const v2Domain = toV2Domain(domainSource);
+  const v2DomainSource = JSON.stringify(v2Domain, null, 2);
+  const v2DomainFile = join(temporaryRoot, "domain-strategy-v2.yaml");
+  await writeFile(v2DomainFile, v2DomainSource);
+  const v2Pass = run(validator, v2DomainFile, temporaryRoot);
+  if (v2Pass.status !== 0) throw new Error(`read-only v2 fixture should pass: ${v2Pass.stderr}`);
+
+  const migratedDomainV3 = spawnSync(process.execPath, [v3MigrationTool, v2DomainFile, "--kind", "domain-strategy", "--root", temporaryRoot], { cwd: projectRoot, encoding: "utf8" });
+  if (migratedDomainV3.status !== 0) throw new Error(`v2 domain strategy should migrate: ${migratedDomainV3.stderr}`);
+  const migratedDomainV3Value = JSON.parse(migratedDomainV3.stdout);
+  if (migratedDomainV3Value.schema_version !== 3 || migratedDomainV3Value.status !== "draft" || migratedDomainV3Value.approval.approval_ref !== "migration-required") throw new Error("domain v2 -> v3 migration must reset approval and status");
+
+  const duplicateRule = join(temporaryRoot, "duplicate-rule.yaml");
+  const duplicateRuleValue = parseYaml(domainSource);
+  duplicateRuleValue.rule_catalog.push(structuredClone(duplicateRuleValue.rule_catalog[0]));
+  await writeFile(duplicateRule, JSON.stringify(duplicateRuleValue, null, 2));
+  expectBlocked(run(validator, duplicateRule, temporaryRoot), /rule_id.*重复|重复.*rule_id/, "duplicate v3 rule id");
+
+  const danglingRule = join(temporaryRoot, "dangling-rule.yaml");
+  const danglingRuleValue = parseYaml(domainSource);
+  danglingRuleValue.scenarios[0].rule_refs = ["rule.missing"];
+  await writeFile(danglingRule, JSON.stringify(danglingRuleValue, null, 2));
+  expectBlocked(run(validator, danglingRule, temporaryRoot), /rule_refs.*未声明|悬空/, "dangling v3 rule ref");
+
+  const missingEvidence = join(temporaryRoot, "missing-rule-evidence.yaml");
+  const missingEvidenceValue = parseYaml(domainSource);
+  missingEvidenceValue.rule_catalog[0].evidence_refs = [];
+  await writeFile(missingEvidence, JSON.stringify(missingEvidenceValue, null, 2));
+  expectBlocked(run(validator, missingEvidence, temporaryRoot), /evidence_refs/, "missing v3 evidence");
 
   const legacyFile = join(temporaryRoot, "legacy-domain.yaml");
-  await writeFile(legacyFile, domainSource.replace("schema_version: 2", "schema_version: 1"));
+  await writeFile(legacyFile, JSON.stringify({ ...v2Domain, schema_version: 1 }, null, 2));
   expectBlocked(run(validator, legacyFile, temporaryRoot), /migration-required/, "legacy domain contract");
 
   const migratableLegacy = join(temporaryRoot, "migratable-legacy-domain.yaml");
-  const migratableLegacySource = domainSource
-    .replace("schema_version: 2", "schema_version: 1")
-    .replace(/context_snapshot:\n[\s\S]*?\ndownstream_mapping:/, "terminology_refs: [CONTEXT.md#Supplier, contexts/ComplianceReview/CONTEXT.md#AdmissionDecision]\ndownstream_mapping:");
+  const migratableLegacyValue = { ...structuredClone(v2Domain), schema_version: 1, terminology_refs: ["CONTEXT.md#Supplier", "contexts/ComplianceReview/CONTEXT.md#AdmissionDecision"] };
+  delete migratableLegacyValue.context_snapshot;
+  const migratableLegacySource = JSON.stringify(migratableLegacyValue, null, 2);
   await writeFile(migratableLegacy, migratableLegacySource);
   const migrated = spawnSync(process.execPath, [migrationTool, migratableLegacy, "--root", temporaryRoot], { cwd: projectRoot, encoding: "utf8" });
   if (migrated.status !== 0) throw new Error(`migratable v1 contract should migrate: ${migrated.stderr}`);
@@ -91,7 +168,7 @@ try {
   if (migratedValue.schema_version !== 2 || migratedValue.terminology_refs !== undefined || migratedValue.context_snapshot.context_ref !== "CONTEXT.md" || migratedValue.context_snapshot.term_refs.join(",") !== "ComplianceReview/AdmissionDecision,Global/Supplier") throw new Error("migrated context snapshot is incomplete");
 
   const ambiguousLegacy = join(temporaryRoot, "ambiguous-legacy-domain.yaml");
-  await writeFile(ambiguousLegacy, migratableLegacySource.replace("CONTEXT.md#Supplier, contexts/ComplianceReview/CONTEXT.md#AdmissionDecision", "contexts/ComplianceReview/CONTEXT.md"));
+  await writeFile(ambiguousLegacy, JSON.stringify({ ...migratableLegacyValue, terminology_refs: ["contexts/ComplianceReview/CONTEXT.md"] }, null, 2));
   const ambiguousMigration = spawnSync(process.execPath, [migrationTool, ambiguousLegacy, "--root", temporaryRoot], { cwd: projectRoot, encoding: "utf8" });
   expectBlocked(ambiguousMigration, /migration-required.*无法唯一定位|无法唯一定位.*migration-required/, "ambiguous legacy reference");
 
@@ -115,32 +192,48 @@ try {
   await writeFile(unknownContext, domainSource.replace("to_context: ComplianceReview", "to_context: UnknownContext"));
   expectBlocked(run(validator, unknownContext, temporaryRoot), /未引用已声明上下文|未在领域战略中登记/, "unknown context");
 
-  const packageApprovalRef = join(temporaryRoot, "package-approval.json");
   const packageSource = (await readFile(validPackageTemplate, "utf8"))
-    .replace(".agents/skills/yss-stage-decision/tests/fixtures/stage-decision-approval.yaml", packageApprovalRef)
     .replace("<document-digest>", context.document_digest)
     .replace("<referenced-terms-digest>", context.referenced_terms_digest)
     .replace("<domain-strategy-digest>", digestYaml(domainSource));
   const packageFile = join(temporaryRoot, "stage-decision.yaml");
   await writeFile(packageFile, packageSource);
-  const packageDecision = buildDecisionFixture(join(temporaryRoot, "package-decision"), { boundary: "check.stage-decision-package-approved", subjectRef: packageFile });
-  const packageApproval = parseDocument(await readFile(join(testsRoot, "fixtures/stage-decision-approval.yaml"), "utf8")).toJS();
-  await writeFile(packageApprovalRef, JSON.stringify({ ...packageApproval, subject_ref: packageFile, approval_scope: packageDecision.requirement.scope, user_decision_ref: packageDecision.ref }));
   const packagePass = run(packageValidator, packageFile, temporaryRoot);
-  if (packagePass.status !== 0) throw new Error(`valid v2 stage decision package should pass: ${packagePass.stderr}`);
+  if (packagePass.status !== 0) throw new Error(`valid v3 stage decision package should pass: ${packagePass.stderr}`);
+
+  const v2Stage = toV2Stage(packageSource, digestYaml(v2DomainSource));
+  const v2StageFile = join(temporaryRoot, "stage-decision-v2.yaml");
+  await writeFile(v2StageFile, JSON.stringify(v2Stage, null, 2));
+  const v2StagePass = run(packageValidator, v2StageFile, temporaryRoot);
+  if (v2StagePass.status !== 0) throw new Error(`read-only v2 stage decision package should pass: ${v2StagePass.stderr}`);
+
+  const migratedV3 = spawnSync(process.execPath, [v3MigrationTool, v2StageFile, "--kind", "stage-decision", "--root", temporaryRoot], { cwd: projectRoot, encoding: "utf8" });
+  if (migratedV3.status !== 0) throw new Error(`v2 stage decision should migrate: ${migratedV3.stderr}`);
+  const migratedV3Value = JSON.parse(migratedV3.stdout);
+  if (migratedV3Value.schema_version !== 3 || migratedV3Value.status !== "draft" || migratedV3Value.approval.approval_ref !== "migration-required") throw new Error("v2 -> v3 migration must reset approval and status");
+
+  const wrongSourceRef = join(temporaryRoot, "stage-decision-wrong-source-ref.yaml");
+  const wrongSourceRefValue = parseYaml(packageSource);
+  wrongSourceRefValue.success_criteria[0].source_refs = ["rule.missing"];
+  await writeFile(wrongSourceRef, JSON.stringify(wrongSourceRefValue, null, 2));
+  expectBlocked(run(packageValidator, wrongSourceRef, temporaryRoot), /source_refs.*未在领域战略中声明|悬空/, "stage decision dangling source ref");
 
   const packageLegacy = join(temporaryRoot, "legacy-stage-decision.yaml");
-  await writeFile(packageLegacy, packageSource.replace("schema_version: 2", "schema_version: 1"));
+  await writeFile(packageLegacy, JSON.stringify({ ...v2Stage, schema_version: 1 }, null, 2));
   expectBlocked(run(packageValidator, packageLegacy, temporaryRoot), /migration-required/, "legacy stage decision contract");
 
   const packageBlocker = join(temporaryRoot, "stage-decision-blocker.yaml");
-  await writeFile(packageBlocker, packageSource.replace("type: deferred", "type: blocker"));
+  const blockerValue = parseYaml(packageSource);
+  blockerValue.unresolved_items[0].type = "blocker";
+  await writeFile(packageBlocker, JSON.stringify(blockerValue, null, 2));
   expectBlocked(run(packageValidator, packageBlocker, temporaryRoot), /blocker/, "blocker package");
 
   const packageWrongArray = join(temporaryRoot, "stage-decision-wrong-array.yaml");
-  await writeFile(packageWrongArray, packageSource.replace("target_users: [采购专员、合规专员]", "target_users: [42]"));
+  const wrongArrayValue = parseYaml(packageSource);
+  wrongArrayValue.target_users = [42];
+  await writeFile(packageWrongArray, JSON.stringify(wrongArrayValue, null, 2));
   expectBlocked(run(packageValidator, packageWrongArray, temporaryRoot), /target_users\[0\]/, "package non-string array item");
 } finally {
   await rm(temporaryRoot, { recursive: true, force: true });
 }
-process.stdout.write("业务边界与规则设计 v2 场景验证通过\n");
+process.stdout.write("业务边界与规则设计 v2/v3 场景验证通过\n");

package/template/.agents/skills/yss-technical-design/SKILL.md

@@ -7,6 +7,12 @@ description: 在 YSS 技术分析中统一承接需求与战略输入，按已
 
 由 `yss-product-lifecycle` 调度，负责 `work-unit.technical-analysis` 的技术设计，不另起生命周期、不生成生产代码。生命周期维护批准和状态；`yss-implementation-contract-compiler` 消费批准且当前的设计，起草实现合同。
 
+文档输出时按 `lifecycle-document-output` 条件调用 `i-have-adhd`，读取 `docs/process/document-writing.md`；作用域仅限当前产物，派发时传递条件及引用。
+
+## 文档写作
+
+起草或修订技术设计解释正文前，读取 `docs/process/document-writing.md` 的共用写法及工程契约指引，并在分支派发中传递该引用；结构化合同保持原 schema 和验证要求。
+
 ## 输入与架构选择
 
 先读根 `CONTEXT.md`、已批准且当前的 Spec、业务规则、关键场景、适用的 API 契约、ADR 和工程约束。没有 API 或其他专项影响时记录有依据的不适用，不生成占位设计。

package/template/.codex/skills/archify/SKILL.md

@@ -16,7 +16,7 @@ Create a self-contained, interactive HTML diagram from a small typed JSON specif
 
 When the current repository contains `yss-project.yaml`, these rules override the upstream update and delivery commands below:
 
-- Treat Archify as a conditional specialist. Use it only when the user or the current YSS contract explicitly requires an architecture, workflow, sequence, data-flow, lifecycle, or Mermaid-beautification artifact. A diagram is derived evidence; it never replaces Spec, ADR, OpenAPI, Tactical Design Contract, Slice Implementation Contract, review, or approval evidence.
+- Treat Archify as a conditional specialist. Use it only when the user or the current YSS contract explicitly requires an architecture, workflow, sequence, data-flow, lifecycle, or Mermaid-beautification artifact. A diagram is derived evidence; it never replaces the active profile's architecture contract (such as backend Tactical Design or Frontend Engineering Design), Spec, ADR, OpenAPI, Slice Implementation Contract, review, or approval evidence.
 - Do not run `scripts/check-update.mjs`. YSS pins the upstream revision in `skills-lock.json`; upgrades happen only through the repository's skill-maintenance workflow.
 - Validate with the upstream `validate` command, but deliver through the repository-safe wrapper from the repository root:
 

package/template/.codex/skills/code-review/SKILL.md

@@ -13,6 +13,12 @@ Standards and Spec run as **parallel sub-agents** so they don't pollute each oth
 
 If `docs/agents/issue-tracker.md` is missing, tell the user to run `/setup-matt-pocock-skills`; do not invoke another user-invoked skill yourself.
 
+文档输出时按 `lifecycle-document-output` 条件调用 `i-have-adhd`，读取 `docs/process/document-writing.md`；作用域仅限当前产物，派发时传递条件及引用。
+
+## 文档写作
+
+撰写审查报告时，读取 `docs/process/document-writing.md` 的共用写法及审查指引；保留各审查轴的 findings、严重性、定位、证据及原裁决，不因压缩表达合并或降级。
+
 ## Process
 
 ### 1. Pin the fixed point and candidate

package/template/.codex/skills/i-have-adhd/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Ayoub Ghriss
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/template/.codex/skills/i-have-adhd/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: i-have-adhd
+description: 在研发文档起草、修订、审查报告和交接表达时，按 YSS 中文规范组织具体、完整、可执行的输出；仅作用于当前文档工作。
+license: MIT
+---
+
+# i-have-adhd · YSS 适配
+
+为当前产物应用 `docs/process/document-writing.md`；该文是中文写法的唯一权威来源。需要例子时读取 `docs/templates/examples/lifecycle-writing-examples.md`。本技能是原资产所有者的配套技能，不持有业务决定、批准或生命周期状态。
+
+## 触发与作用域
+
+调用者在当前工作包含研究结论、Plan、Spec、设计说明、契约解释正文、Ticket、审查、交接、发布或复盘时，设置条件 `lifecycle-document-output` 并加载本技能。进度与会签表达也属于文档输出；纯代码修改、命令执行和后续无关会话不激活此条件。
+
+每次调用只覆盖输入指定的文档或报告。工作结束即结束本次作用域；用户后续要求正常表达或不使用本技能时遵从当前要求，不继承先前启用状态。不假设读者具有任何诊断。
+
+## 执行
+
+1. 接收产物类型、读者、允许改动范围和可读权威输入；先读共用规范，再读取对应阶段指引。字段、版本或规则来源不明确时保留缺口并回交原所有者，不补造业务决定。
+2. 先写当前问题、结论或交付行为，再提供依据和必要细节；按顺序动作、规则比较和因果说明选择编号、表格或段落。删除无信息的修饰和重复，不设置字数或规则数量上限。
+3. 对照输入核查主体、条件、例外、量词、范围、数值、证据、未决项、责任、时点和依赖。保持原 API 标识、schema、冻结行为、状态及批准证据；发现冲突时交回所有者，不以润色名义修复事实。
+4. 返回调整后的正文及必要的缺口说明，由原工作单元执行现有验证。明确区分已验证结果、估算和未知原因；未执行测试不写通过，多项实质阻塞全部保留。已授权工作由原执行者继续，不把可完成的操作转交用户。
+
+研究仍使用原研究证据合同；代码审查保留原轴、严重性、定位和结论；契约保持机器结构。共用规范不可读时停止受影响的文档改写并报告缺失引用，不妨碍独立的已授权工作。
+
+来源、固定版本和适配差异见 [YSS 适配说明](references/yss-adaptation.md)。只安装项目技能，不安装上游全局插件、hook 或会话持久模式。

package/template/.codex/skills/i-have-adhd/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "i-have-adhd · YSS 文档配套"
+  short_description: "按当前研发文档任务应用中文写作规范，保持规则与证据完整"
+  default_prompt: "使用 i-have-adhd 配套技能改善当前研发文档表达，保留所有业务规则、证据、未决项和原批准状态。"
+policy:
+  allow_implicit_invocation: true

package/template/.codex/skills/i-have-adhd/references/yss-adaptation.md

@@ -0,0 +1,21 @@
+# i-have-adhd 的 YSS 适配
+
+上游：`ayghri/i-have-adhd`；固定 revision：`7b9069b39972e269e61bd95c2f66ebb90cac6a02`；许可证见技能目录 `LICENSE`。
+
+原始文件来自 [固定版本目录](https://github.com/ayghri/i-have-adhd/tree/7b9069b39972e269e61bd95c2f66ebb90cac6a02/skills/i-have-adhd)。未经改写的来源基线保存在模板维护证据中；`upstream-files.json` 记录逐文件 SHA-256，`skills-lock.json` 记录上游目录哈希和当前技能目录哈希。基线不进入实例默认加载面。
+
+| 上游行为 | YSS 适配 |
+|---|---|
+| 用户显式调用、会话持续 | 原技能名保留；文档工作按 `lifecycle-document-output` 条件调用，任务结束即失效 |
+| 对读者作 ADHD 假设 | 面向所有文档读者，不引入诊断假设 |
+| 行动前置、步骤编号、删除套话 | 消费中文写作规范，按产物类型决定信息顺序和格式 |
+| 展示进度、下一步和具体时间 | 报告实际变化和全部必要阻塞；时间有依据才估算，不把工作推给用户 |
+| 压缩可见列表 | 完整性优先，不设规则数量上限 |
+| 原因与修复直接陈述 | 区分已知现象、待验证原因和实际验证结果 |
+| 平台专属 agent 配置 | 不安装上游 Gemini 持久提示；项目 OpenAI 配置只描述当前文档配套用途 |
+
+生命周期仍拥有门禁、状态、批准和资产；本技能没有独立授权、审批或分支流程。正文规则只在 `docs/process/document-writing.md` 维护；本文件只解释来源差异。
+
+注册表将本技能声明为模型可调用、实例默认可发现的通用工作流 core 技能（仍只作为文档配套）；调用者以条件依赖加载。上游 `disable-model-invocation: true` 在适配版移除；作用域由本技能触发条件限定，不延续上游会话开关。
+
+验证只证明来源、路由、投影和合同符合预期。中文文档质量需通过真实生成评估，不以结构检查或作者自检代替盲评效果。

package/template/.codex/skills/i-have-adhd/tests/verify-integration.mjs

@@ -0,0 +1,63 @@
+// Structural and real dependency-resolution checks; not a model-output quality evaluation.
+import assert from 'node:assert/strict';
+import fs from 'node:fs';
+import path from 'node:path';
+import {pathToFileURL} from 'node:url';
+
+const root=path.resolve(process.argv[2] || '.');
+const read=ref=>fs.readFileSync(path.join(root,ref),'utf8');
+const {parse}=await import(pathToFileURL(path.join(root,'scripts/vendor/yaml.mjs')));
+const registry=parse(read('docs/agents/yss-skill-registry.yaml'));
+const skill=registry.skills.find(x=>x.id==='i-have-adhd');
+assert.equal(skill.instance_default_discoverable,true);
+assert.equal(registry.invocation_contract.overrides['i-have-adhd'].invocation_mode,'model');
+assert.ok(registry.invocation_contract.overrides['i-have-adhd'].exclusion_conditions.includes('unrelated-conversation'));
+assert.ok(registry.invocation_contract.overrides['i-have-adhd'].exclusion_conditions.includes('user-disabled'));
+const entry=read('.agents/skills/i-have-adhd/SKILL.md');
+assert.ok(!entry.includes('disable-model-invocation: true'));
+assert.equal(parse(read('.agents/skills/i-have-adhd/agents/openai.yaml')).policy.allow_implicit_invocation,true);
+const lock=JSON.parse(read('skills-lock.json'));
+const locked=lock.skills.shared['i-have-adhd'];
+assert.equal(locked.source,'ayghri/i-have-adhd');
+assert.equal(locked.sourceRevision,'7b9069b39972e269e61bd95c2f66ebb90cac6a02');
+assert.notEqual(locked.upstreamHash,locked.effectiveHash);
+const {treeHash}=await import(pathToFileURL(path.join(root,'scripts/lib/skill-supply-chain.mjs')));
+assert.equal(treeHash(path.join(root,'.agents/skills/i-have-adhd')),locked.effectiveHash);
+for (const target of locked.targets) {
+  const skillPath=target.endsWith('/i-have-adhd')?target:path.join(target,'i-have-adhd');
+  assert.equal(treeHash(path.join(root,skillPath)),locked.effectiveHash,`projection ${target}`);
+}
+for(const ref of ['docs/process/document-writing.md','docs/templates/examples/lifecycle-writing-examples.md']) {
+  assert.ok(read(ref).length);
+  assert.ok(!read(ref).includes('.template-source/'));
+}
+const callers=Object.entries(registry.skill_dependencies).filter(([,deps])=>deps.some(d=>d.skill==='i-have-adhd'));
+assert.ok(callers.length>0);
+for(const [owner,deps] of callers) {
+  const edge=deps.find(d=>d.skill==='i-have-adhd');
+  assert.equal(edge.type,'context-conditional');
+  assert.equal(edge.when,'lifecycle-document-output');
+  assert.ok(read(`.agents/skills/${owner}/SKILL.md`).includes('`i-have-adhd`'));
+}
+const orchestrator=registry.skills.find(x=>['yss-product-lifecycle','yss-strategic-design','harness-orchestrator'].includes(x.id)).id;
+const contract=parse(read(`.agents/skills/${orchestrator}/references/orchestration-contract.yaml`));
+assert.equal(contract.document_writing.supporting_skill,'i-have-adhd');
+assert.equal(contract.document_writing.condition,'lifecycle-document-output');
+assert.equal(contract.document_writing.scope,'current-document-work-only');
+assert.equal(contract.document_writing.gate_and_status_semantics,'unchanged');
+
+// Compile using the actual repository resolver, with and without the condition and again without it.
+const compiler=path.join(root,'scripts/lib/implementation-contract-compiler.mjs');
+if(fs.existsSync(compiler)) {
+  const api=await import(pathToFileURL(compiler));
+  const capability=registry.capabilities.find(c=>c.id==='governance.implementation-contract');
+  assert.ok(capability);
+  const run=conditions=>api.compileImplementationContract({registry,compilerContract:api.loadCompilerContract(),requiredCapabilities:[capability.id],conditions,root});
+  const off=run([]),on=run(['lifecycle-document-output']),next=run([]);
+  assert.ok(!off.required_skills.includes('i-have-adhd'));
+  assert.ok(on.required_skills.includes('i-have-adhd'));
+  assert.ok(!next.required_skills.includes('i-have-adhd'));
+  assert.equal(on.status,'draft');
+  console.log('PASS: actual resolver excludes code-only, includes document output, does not persist condition or approve the contract.');
+} else console.log('N/A: this strategic-only template has no implementation compiler; conditional route verified in registry and orchestration contract.');
+console.log(`PASS: source, license metadata, ${locked.targets.length} projections, ${callers.length} callers, scope and readable writing inputs. Model output quality not measured.`);

package/template/.codex/skills/prototype-review/SKILL.md

@@ -7,6 +7,8 @@ description: Use when independently reviewing low-fidelity UI, interaction specs
 
 Use this skill as the independent low-fidelity review in `yss-prototype-stage`. The review is fail-closed: if the design cannot drive calibrated requirements, API, frontend acceptance, and slices, send it back to product design. `yss-product-lifecycle` alone records the resulting `check.prototype-reviewed` decision.
 
+文档输出时按 `lifecycle-document-output` 条件调用 `i-have-adhd`，读取 `docs/process/document-writing.md`；作用域仅限当前产物，派发时传递条件及引用。
+
 ## Trigger Boundary
 
 Run this independent gate only when UI changes affect a primary user flow, navigation, permissions, exception/recovery states, state transitions, or OpenAPI implications. For copy edits, token/color/spacing adjustments, and isolated visual fixes with no behavior, state, permission, navigation, or API impact, record `not-applicable` with the impact assessment; do not create prototype-review artifacts.

package/template/.codex/skills/yss-implementation-contract-compiler/SKILL.md

@@ -7,6 +7,12 @@ description: Use when a YSS vertical slice is entering implementation, spans mul
 
 阶段 7 的实现合同编译器。它把已批准的生命周期资产、垂直切片、capability 和窄 Recipe 编译为 `Slice Implementation Contract` v2 草案；不批准合同、不写业务代码、不设置 `ready-for-agent`。
 
+文档输出时按 `lifecycle-document-output` 条件调用 `i-have-adhd`，读取 `docs/process/document-writing.md`；作用域仅限当前产物，派发时传递条件及引用。
+
+## 文档写作
+
+撰写实现合同的解释正文和切片交接说明前，读取 `docs/process/document-writing.md` 的共用写法及工程契约 / Ticket 指引；不改变结构化合同、批准状态或就绪条件。
+
 ## 输入
 
 先读取 Spec、切片 Ticket、需求冻结、适用的原型确认、OpenAPI Freeze/no-impact、系统/数据架构、Design Review、Build Architecture Checklist、实现仓库和验证命令。输入缺失、未批准或 `stale` 时输出 `blocked`，交回 `yss-product-lifecycle`。

package/template/.codex/skills/yss-implementation-contract-compiler/references/boundaries.md

@@ -18,6 +18,7 @@
 
 | Capability | Primary skill | Task modes |
 | --- | --- | --- |
+| `writing.lifecycle-document` | `i-have-adhd` | `guidance` |
 | `architecture.technical-design` | `yss-technical-design` | `guidance`, `integration`, `review-input` |
 | `architecture.mvc-design` | `yss-mvc-design` | `guidance`, `integration`, `review-input` |
 | `layer.mvc-service` | `yss-application` | `guidance`, `integration`, `slice-implementation`, `troubleshooting`, `review-input` |
@@ -105,8 +106,16 @@
 
 | Skill | Dependency | Type | Condition |
 | --- | --- | --- | --- |
+| `prototype-review` | `i-have-adhd` | `context-conditional` | `lifecycle-document-output` |
+| `yss-implementation-contract-compiler` | `i-have-adhd` | `context-conditional` | `lifecycle-document-output` |
+| `yss-openapi-governance` | `i-have-adhd` | `context-conditional` | `lifecycle-document-output` |
+| `yss-stage-decision` | `i-have-adhd` | `context-conditional` | `lifecycle-document-output` |
+| `yss-research` | `i-have-adhd` | `context-conditional` | `lifecycle-document-output` |
+| `yss-product-lifecycle` | `i-have-adhd` | `context-conditional` | `lifecycle-document-output` |
+| `code-review` | `i-have-adhd` | `context-conditional` | `lifecycle-document-output` |
 | `code-review` | `yss-repository` | `context-conditional` | `backend-persistence-impact` |
 | `code-review` | `yss-mybatis` | `context-conditional` | `backend-persistence-impact` |
+| `yss-prototype-stage` | `i-have-adhd` | `context-conditional` | `lifecycle-document-output` |
 | `yss-prototype-stage` | `prototype-review` | `review-only` | — |
 | `yss-prototype-stage` | `yss-design-system` | `coordination-only` | — |
 | `yss-prototype-stage` | `yss-antdv-next-design` | `context-conditional` | `h2-vue-antdv-next-default` |
@@ -118,6 +127,7 @@
 | `yss-domain` | `domain-modeling` | `coordination-only` | — |
 | `yss-domain` | `yss-tactical-design` | `context-conditional` | `tactical-domain` |
 | `yss-domain` | `lombok` | `context-conditional` | `pojo` |
+| `yss-technical-design` | `i-have-adhd` | `context-conditional` | `lifecycle-document-output` |
 | `yss-technical-design` | `yss-tactical-design` | `coordination-only` | `domain-driven` |
 | `yss-technical-design` | `yss-mvc-design` | `coordination-only` | `layered-mvc` |
 | `yss-mvc-design` | `yss-openapi-draft-review` | `review-only` | `api-impact` |

package/template/.codex/skills/yss-openapi-governance/SKILL.md

@@ -15,6 +15,12 @@ Spec / 设计输入 → OpenAPI YAML Draft → 审查与 Freeze → JSON 派生
 
 YSS DTO 的可复用 HTTP/JSON 映射由 `.agents/skills/yss-dto/references/openapi-wire-profile.yaml` 单一维护。它描述公开 wire shape，不是 Java 字段或 getter 清单；本 skill 必须消费 profile，不能在治理文档、feature YAML 和 JSON 中各自发明 `SingleResult`、`PageResult` 或 `PageQuery` 字段表。
 
+文档输出时按 `lifecycle-document-output` 条件调用 `i-have-adhd`，读取 `docs/process/document-writing.md`；作用域仅限当前产物，派发时传递条件及引用。
+
+## 文档写作
+
+编写接口说明和契约评审交接正文前，读取 `docs/process/document-writing.md` 的共用写法及工程契约指引；协议标识、schema、冻结状态和验证记录按原合同保存。
+
 ## 边界与职责
 
 使用 `yss-openapi-governance`：