tech-lead-skill 5.4.7 → 5.4.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -35,7 +35,7 @@ The source set was scanned for local absolute paths, passwords, API-key prefixes
35
35
  ### Structural scan
36
36
 
37
37
  - YAML frontmatter has `name: tech-lead` and a trigger description.
38
- - The skill version is `v5.4.7`.
38
+ - The skill version is `v5.4.8`.
39
39
  - The eight templates referenced by the skill exist.
40
40
  - The installer validates options, requires a marker before removing any target, and records the managed package/version after installation.
41
41
  - The release-check template covers allowlist inventory, sensitive-content scanning, reference checks, scope checks, publication results, and remote verification.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tech-lead-skill",
3
- "version": "5.4.7",
3
+ "version": "5.4.8",
4
4
  "description": "Evidence-driven planning and safe change-control skill for OpenCode-compatible agents",
5
5
  "license": "MIT",
6
6
  "repository": {
package/skill/SKILL.md CHANGED
@@ -3,7 +3,7 @@ name: tech-lead
3
3
  description: 用于软件、基础设施、研究和运维中的多步、跨边界或有状态工程交付:项目规划、架构选择、跨模块实现、部署、迁移、发布、恢复、重构、长期运行与跨会话续跑。涉及不可逆/生产变更、回滚验证、真实环境对账、发布安全或项目级交付治理时优先加载,即使用户没有说“项目”或“Tech Lead”。不要仅因一次性小修复、单文件编辑、普通解释、单次测试或只读代码审查而自动加载,除非用户明确要求项目级计划或本规范。
4
4
  ---
5
5
 
6
- # Tech Lead · 自主演进规划与交付规范 v5.4.7
6
+ # Tech Lead · 自主演进规划与交付规范 v5.4.8
7
7
 
8
8
  > 双层架构声明:本文件是**判断层**(自由裁量域)。其中可机械判定的不变量(Gate 前置校验、
9
9
  > 证据锚点存在性、分级判定器、状态机转换有效性)为未来 **MCP 工具化候选**——
@@ -64,7 +64,7 @@ M0 前列 ≤5 个关键假设请用户确认;目标、Non-Goals 和不可逆
64
64
  ### 4.0 介入哲学
65
65
  低风险、可逆且已授权范围内的步骤可依环境证据自主推进;能跑通的证据优先于重复请示。
66
66
  生产停机/重启、数据库迁移、权限或账户变更、秘密轮换、外部网络请求、公开发布、成本增加和可能影响用户数据的批量操作,必须有明确授权或项目既有变更审批。
67
- 派发给子代理的是「目标+判据+边界」,永远不是步骤脚本。
67
+ 派发给子代理的是「目标+判据+边界」,永远不是步骤脚本。委派的默认动机是上下文防污染:大体积检索、批量探针、远程诊断与多路评审交给子代理,主会话只回收结论与证据锚点——除非任务本身需要逐步共享状态,才留在主会话执行。
68
68
 
69
69
  ### 4.1 计划分辨率金字塔
70
70
  - L0 骨架层(§3):回答"是什么"。