tech-lead-skill 5.4.7 → 5.4.9
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.
- package/README.md +2 -2
- package/README.zh-CN.md +1 -1
- package/docs/AUDIT_REPORT.md +1 -1
- package/package.json +1 -1
- package/skill/SKILL.md +2 -2
package/README.md
CHANGED
|
@@ -50,10 +50,10 @@ The installer is idempotent: repeated runs back up existing files as `*.bak-<tim
|
|
|
50
50
|
|
|
51
51
|
### DeepSeek Harness plugin (read-only tools)
|
|
52
52
|
|
|
53
|
-
Ships on the DSH plugin market (npm) as ONE self-contained package. Install into any profile:
|
|
53
|
+
Ships on the DSH plugin market (npm) as ONE self-contained package, **`dsh-themis`** — named after the goddess of divine order: gates as verdicts, evidence weighed, releases audited. Install into any profile:
|
|
54
54
|
|
|
55
55
|
```
|
|
56
|
-
dsh plugin --profile headless add
|
|
56
|
+
dsh plugin --profile headless add dsh-themis
|
|
57
57
|
```
|
|
58
58
|
|
|
59
59
|
21 read-only lifecycle tools in a single artifact (the original nine audits plus context validation, evidence graph/freshness analysis, progress decisions, critical-path/impact analysis, resume reconciliation, gate planning/aggregation/reopen checks, and mutation preview). Tools compute over caller-supplied JSON only — no filesystem writes, no subprocesses, no network access. The earlier split packages (`dsh-tech-lead-{core,plugin,bundle}`) are deprecated in favor of this one. Source checkouts remain supported: build via `node scripts/build-market-package.mjs` then `dsh plugin add packages/dsh-tech-lead`. The root npm package distributes the skill and installer only.
|
package/README.zh-CN.md
CHANGED
|
@@ -53,7 +53,7 @@ npx github:240xu/tech-lead-skill
|
|
|
53
53
|
已上架 DSH 插件市场(npm)——**单一自包含包**,任意 profile 一键安装:
|
|
54
54
|
|
|
55
55
|
```
|
|
56
|
-
dsh plugin --profile headless add
|
|
56
|
+
dsh plugin --profile headless add dsh-themis
|
|
57
57
|
```
|
|
58
58
|
|
|
59
59
|
单包内含全部 21 个只读生命周期工具:原九项审计+上下文校验、证据图/新鲜度分析、推进决策、关键路径/影响分析、续跑对账、Gate 计划/聚合/重开、变更预览。仅对调用方传入的 JSON 做计算——无文件写入、无子进程、无网络访问。旧拆分包(`dsh-tech-lead-{core,plugin,bundle}`)已弃用并指向本包。源码安装:`node scripts/build-market-package.mjs` 装配后 `dsh plugin add packages/dsh-tech-lead`。根 npm 包只发布技能与安装器。
|
package/docs/AUDIT_REPORT.md
CHANGED
|
@@ -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.
|
|
38
|
+
- The skill version is `v5.4.9`.
|
|
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
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.
|
|
6
|
+
# Tech Lead · 自主演进规划与交付规范 v5.4.9
|
|
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):回答"是什么"。
|