dic-workflow-kit 1.1.0 → 1.1.1

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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dic-workflow-kit",
3
- "version": "1.1.0",
3
+ "version": "1.1.1",
4
4
  "description": "Design-implementation consistency workflow with OpenSpec obligations, BDD knowledge, Skills, and Subagents.",
5
5
  "author": {
6
6
  "name": "TonyClaw"
package/CHANGELOG.md ADDED
@@ -0,0 +1,47 @@
1
+ # Changelog
2
+
3
+ All notable changes to DIC Workflow Kit are documented in this file.
4
+
5
+ The project follows [Semantic Versioning](https://semver.org/). Both npm packages, `dic-workflow-kit` and `@tonyclaw/dic-workflow-kit`, always use the same version and runtime payload.
6
+
7
+ ## [1.1.1] - 2026-07-27
8
+
9
+ ### Added
10
+
11
+ - Added this changelog.
12
+ - Added complete Chinese and English user guides covering installation, workflow prompts, OpenSpec Change usage, output interpretation, and troubleshooting.
13
+
14
+ ### Changed
15
+
16
+ - Made the unscoped `npx dic-workflow-kit@<version>` command the recommended one-shot installation entry for consistent Windows behavior.
17
+ - Updated version synchronization so both scoped and unscoped npm examples advance with each release.
18
+
19
+ ### Security and packaging
20
+
21
+ - Kept the npm release as a runtime-only package: no development CLI source, Python helper, tests, release scripts, PowerPoint files, temporary files, or source maps.
22
+ - Retained only the minified installer runtime and the Skills, Subagents, schemas, adapters, manifests, and user documentation required to use the kit.
23
+
24
+ ## [1.1.0] - 2026-07-27
25
+
26
+ ### Added
27
+
28
+ - Added one npm installer for Codex, Claude Code, OpenCode, and MiMo Code.
29
+ - Added user-level and project-level installation for supported hosts.
30
+ - Added host-specific Subagent frontmatter adaptation.
31
+ - Added convergent dual publishing for `dic-workflow-kit` and `@tonyclaw/dic-workflow-kit`.
32
+ - Added isolated installation tests for all four hosts.
33
+
34
+ ### Changed
35
+
36
+ - Promoted the package from a Codex-only installer to a multi-host runtime.
37
+ - Published the CLI as a minified runtime and removed development source files from npm artifacts.
38
+
39
+ ## [1.0.0] - 2026-07-27
40
+
41
+ ### Added
42
+
43
+ - Initial npm release.
44
+ - Included seven workflow and knowledge Skills.
45
+ - Included nine evidence-producing Subagents.
46
+ - Added Codex personal marketplace installation.
47
+ - Added OpenSpec intake, obligation extraction, BDD knowledge, repair planning, validation, and final evidence contracts.
package/README.md CHANGED
@@ -1,6 +1,8 @@
1
1
  # Design-Implementation Consistency Workflow Kit
2
2
 
3
- Version: `1.1.0`
3
+ Version: `1.1.1`
4
+
5
+ [Changelog](CHANGELOG.md)
4
6
 
5
7
  Design-Implementation Consistency Workflow Kit, or DIC Workflow Kit, is a portable agentic workflow package for checking and repairing whether implementation matches design intent.
6
8
 
@@ -17,23 +19,23 @@ The npm package contains all seven Skills and all nine Subagents and installs th
17
19
  Codex remains the default, so the original command is backward compatible:
18
20
 
19
21
  ```text
20
- npx @tonyclaw/dic-workflow-kit@1.1.0 install
22
+ npx dic-workflow-kit@1.1.1 install
21
23
  ```
22
24
 
23
25
  Select another host explicitly:
24
26
 
25
27
  ```text
26
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host claude-code
27
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host opencode
28
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host mimo-code
28
+ npx dic-workflow-kit@1.1.1 install --host claude-code
29
+ npx dic-workflow-kit@1.1.1 install --host opencode
30
+ npx dic-workflow-kit@1.1.1 install --host mimo-code
29
31
  ```
30
32
 
31
33
  User scope is the default. To install into the current repository instead, use `--scope project`:
32
34
 
33
35
  ```text
34
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host claude-code --scope project
35
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host opencode --scope project
36
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host mimo-code --scope project
36
+ npx dic-workflow-kit@1.1.1 install --host claude-code --scope project
37
+ npx dic-workflow-kit@1.1.1 install --host opencode --scope project
38
+ npx dic-workflow-kit@1.1.1 install --host mimo-code --scope project
37
39
  ```
38
40
 
39
41
  The host mappings are:
@@ -50,7 +52,7 @@ On Windows, MiMo Code's user root resolves to `%LOCALAPPDATA%\mimocode`; `MIMOCO
50
52
  You can also install the CLI globally:
51
53
 
52
54
  ```text
53
- npm install --global @tonyclaw/dic-workflow-kit@1.1.0
55
+ npm install --global @tonyclaw/dic-workflow-kit@1.1.1
54
56
  dic-workflow-kit install --host opencode
55
57
  ```
56
58
 
@@ -63,6 +65,100 @@ dic-workflow-kit install
63
65
 
64
66
  Use `--dry-run` to preview the resolved destination, `--install-root <path>` for an isolated host root, or the backward-compatible Codex-only `--marketplace-root <path>`. The Codex installer preserves unrelated marketplace entries and replaces only the entry with the same plugin name. Restart or reload the target coding-agent session after its first Skills/agents directory is created.
65
67
 
68
+ ## How to use it
69
+
70
+ ### 1. Start the Coding Agent in your project root
71
+
72
+ After installation, enter the repository you want to inspect and restart Codex, Claude Code, OpenCode, or MiMo Code. An existing session may not discover a newly created Skills/agents directory immediately.
73
+
74
+ ```text
75
+ cd /path/to/your-project
76
+ ```
77
+
78
+ ### 2. Start the workflow with a prompt
79
+
80
+ This prompt works across all four hosts:
81
+
82
+ ```text
83
+ Use DIC Workflow Kit to check design-implementation consistency in this project.
84
+ First identify authoritative design sources and protected paths, then build the
85
+ project profile. Map source-backed obligations to implementation, inspect gaps,
86
+ plan repairs only where design evidence exists, run project-declared validation,
87
+ and report the final consistency status and residual risks.
88
+ ```
89
+
90
+ For an audit that must not modify code:
91
+
92
+ ```text
93
+ Use DIC Workflow Kit to audit this project without modifying files.
94
+ Report design obligations, implementation gaps, evidence locations,
95
+ recommended repairs, and residual risks.
96
+ ```
97
+
98
+ For an evidence-bounded repair:
99
+
100
+ ```text
101
+ Use DIC Workflow Kit to inspect and repair this project.
102
+ Repair only gaps traceable to authoritative design sources. Run relevant
103
+ validation after each change; stop expanding changes when validation fails
104
+ and record the blocker.
105
+ ```
106
+
107
+ ### 3. Check one OpenSpec Change
108
+
109
+ Provide the Change ID explicitly to reduce search scope and avoid treating historical changes as current truth:
110
+
111
+ ```text
112
+ Use DIC Workflow Kit to check the OpenSpec Change
113
+ 2026-06-09-add-ts-local-skill-source.
114
+ Start from its proposal, design, tasks, and delta specs. Cross-check the current
115
+ stable specs, implementation, and tests. Produce an obligation matrix,
116
+ implementation gaps, and a validation conclusion.
117
+ ```
118
+
119
+ For an archived Change, archived files remain historical context while the promoted current stable Spec becomes the authoritative baseline.
120
+
121
+ ### 4. Invoke the core Skill explicitly
122
+
123
+ On hosts that expose slash Skills, start with:
124
+
125
+ ```text
126
+ /workflow-core
127
+ ```
128
+
129
+ You can also name the required Skills directly:
130
+
131
+ ```text
132
+ Use workflow-core, workflow-intake, workflow-profile, and
133
+ knowledge-openspec to inspect the current OpenSpec change.
134
+ ```
135
+
136
+ You do not need to start all nine Subagents manually. The primary Agent should select roles according to evidence dependencies and require every delegation to produce an artifact consumed by a downstream step.
137
+
138
+ ### 5. Read the results
139
+
140
+ Start with these outputs:
141
+
142
+ | File | Purpose |
143
+ | --- | --- |
144
+ | `reports/project-profile.json` | Project structure, design sources, protected paths, and validation commands |
145
+ | `reports/contract-obligations.md` | Human-readable design obligations with source anchors |
146
+ | `reports/implementation-gaps.md` | Confirmed implementation gaps |
147
+ | `reports/repair-plan.md` | Source-backed repair plan with stop conditions |
148
+ | `reports/final-consistency-report.md` | Final consistency conclusion and residual risks |
149
+ | `reports/FINAL_RESULT.json` | Machine-readable terminal status |
150
+ | `logs/trace/` | Intake, delegation, change, and validation evidence |
151
+
152
+ Terminal status is always `PASS`, `PARTIAL`, `BLOCKED`, or `FAIL`. `PASS` means the evidence chain and validation gates are satisfied, not merely that visible tests happen to pass.
153
+
154
+ ### Troubleshooting
155
+
156
+ - **A Skill or Subagent is missing:** restart the Coding Agent and use `--dry-run` to confirm the resolved install root.
157
+ - **Only this repository should use the kit:** add `--scope project` for Claude Code, OpenCode, or MiMo Code.
158
+ - **The project does not use OpenSpec:** use design documents, APIs, schemas, READMEs, or product requirements as authoritative design sources.
159
+ - **A validation tool is unavailable:** record the missing command and environment evidence, and finish as `BLOCKED` or `PARTIAL`; do not claim success.
160
+ - **Do green tests prove consistency:** no. Requirements, branches, state transitions, side effects, and integration flows must also match the design.
161
+
66
162
  ### Dual npm release
67
163
 
68
164
  Every release publishes the same version and payload under both npm names:
@@ -73,7 +169,7 @@ Every release publishes the same version and payload under both npm names:
73
169
  `package.json` is the canonical version source. Set a new version once; the helper propagates it to the Codex plugin manifest, workflow runtime, all Skills, all Subagents, and both READMEs:
74
170
 
75
171
  ```text
76
- npm run release:set-version -- 1.1.0
172
+ npm run release:set-version -- 1.1.1
77
173
  npm run release:plan
78
174
  npm run release:dual:dry-run
79
175
  npm run release:dual
package/README.zh-CN.md CHANGED
@@ -1,6 +1,8 @@
1
1
  # 设计—实现一致性 Workflow Kit
2
2
 
3
- 版本:`1.1.0`
3
+ 版本:`1.1.1`
4
+
5
+ [更新日志](CHANGELOG.md)
4
6
 
5
7
  Design-Implementation Consistency Workflow Kit,简称 DIC Workflow Kit,是一套可移植的智能体工作流包,用于检查和修复“代码实现是否符合设计意图”。
6
8
 
@@ -15,23 +17,23 @@ npm 包完整包含 7 个 Skills 和 9 个 Subagents,并支持 Codex、Claude
15
17
  Codex 仍是默认宿主,原命令保持兼容:
16
18
 
17
19
  ```text
18
- npx @tonyclaw/dic-workflow-kit@1.1.0 install
20
+ npx dic-workflow-kit@1.1.1 install
19
21
  ```
20
22
 
21
23
  安装到其他宿主时显式指定 `--host`:
22
24
 
23
25
  ```text
24
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host claude-code
25
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host opencode
26
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host mimo-code
26
+ npx dic-workflow-kit@1.1.1 install --host claude-code
27
+ npx dic-workflow-kit@1.1.1 install --host opencode
28
+ npx dic-workflow-kit@1.1.1 install --host mimo-code
27
29
  ```
28
30
 
29
31
  默认是用户级安装;若只希望当前仓库使用,则增加 `--scope project`:
30
32
 
31
33
  ```text
32
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host claude-code --scope project
33
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host opencode --scope project
34
- npx @tonyclaw/dic-workflow-kit@1.1.0 install --host mimo-code --scope project
34
+ npx dic-workflow-kit@1.1.1 install --host claude-code --scope project
35
+ npx dic-workflow-kit@1.1.1 install --host opencode --scope project
36
+ npx dic-workflow-kit@1.1.1 install --host mimo-code --scope project
35
37
  ```
36
38
 
37
39
  | 宿主 | 用户级目录 | 项目级目录 |
@@ -46,7 +48,7 @@ Windows 上 MiMo Code 的用户级根目录为 `%LOCALAPPDATA%\mimocode`;适
46
48
  也可以先全局安装 CLI:
47
49
 
48
50
  ```text
49
- npm install --global @tonyclaw/dic-workflow-kit@1.1.0
51
+ npm install --global @tonyclaw/dic-workflow-kit@1.1.1
50
52
  dic-workflow-kit install --host opencode
51
53
  ```
52
54
 
@@ -59,6 +61,96 @@ dic-workflow-kit install
59
61
 
60
62
  使用 `--dry-run` 预演目标目录,使用 `--install-root <path>` 指定隔离的宿主根目录;Codex 仍兼容 `--marketplace-root <path>`。首次创建 Skills 或 agents 目录后,请重启或重新加载对应 Coding Agent 会话。
61
63
 
64
+ ## 用户如何使用
65
+
66
+ ### 1. 在项目根目录启动 Coding Agent
67
+
68
+ 安装完成后,进入需要检查的代码仓库,重新启动 Codex、Claude Code、OpenCode 或 MiMo Code。第一次安装新 Skills/agents 目录时,已有会话可能无法立即发现它们。
69
+
70
+ ```text
71
+ cd /path/to/your-project
72
+ ```
73
+
74
+ ### 2. 用自然语言启动工作流
75
+
76
+ 下面这条提示词适用于四种宿主:
77
+
78
+ ```text
79
+ 使用 DIC Workflow Kit 检查当前项目的设计—实现一致性。
80
+ 先识别权威设计源和受保护路径,生成项目画像;
81
+ 然后建立需求义务、检查实现缺口,只对有设计证据的问题规划修复;
82
+ 运行项目声明的验证命令,最后输出一致性结论和残余风险。
83
+ ```
84
+
85
+ 如果只希望审计、不允许修改代码:
86
+
87
+ ```text
88
+ 使用 DIC Workflow Kit 审计当前项目,但不要修改任何文件。
89
+ 输出设计义务、实现缺口、证据位置、建议修复和残余风险。
90
+ ```
91
+
92
+ 如果希望检查并修复:
93
+
94
+ ```text
95
+ 使用 DIC Workflow Kit 检查并修复当前项目。
96
+ 仅修复能够追溯到权威设计源的缺口;每次修改后执行相关验证,
97
+ 验证失败时停止扩散修改并记录阻塞原因。
98
+ ```
99
+
100
+ ### 3. 检查一个 OpenSpec Change
101
+
102
+ 明确给出 Change ID,可以减少搜索范围并避免把历史 Change 当成当前事实:
103
+
104
+ ```text
105
+ 使用 DIC Workflow Kit 检查 OpenSpec Change
106
+ 2026-06-09-add-ts-local-skill-source。
107
+ 以该 Change 的 proposal、design、tasks 和增量 specs 为入口,
108
+ 同时核对当前稳定 specs、实现和测试,输出义务矩阵、实现缺口和验证结论。
109
+ ```
110
+
111
+ 如果 Change 已归档,工作流会将归档内容作为历史上下文,并以当前已经提升的稳定 Spec 为权威基线。
112
+
113
+ ### 4. 显式调用核心 Skill
114
+
115
+ 支持斜杠 Skill 的宿主可以先输入:
116
+
117
+ ```text
118
+ /workflow-core
119
+ ```
120
+
121
+ 也可以在提示词中直接写出需要使用的 Skill:
122
+
123
+ ```text
124
+ 使用 workflow-core、workflow-intake、workflow-profile 和
125
+ knowledge-openspec 检查当前 OpenSpec 变更。
126
+ ```
127
+
128
+ 不需要手工逐个启动 9 个 Subagents。主 Agent 应按照证据依赖关系选择角色,并保证每个委派都有被下游消费的产物。
129
+
130
+ ### 5. 查看结果
131
+
132
+ 默认应重点查看:
133
+
134
+ | 文件 | 用途 |
135
+ | --- | --- |
136
+ | `reports/project-profile.json` | 项目结构、设计源、保护路径和验证命令 |
137
+ | `reports/contract-obligations.md` | 人可读的设计义务与来源 |
138
+ | `reports/implementation-gaps.md` | 已确认的实现缺口 |
139
+ | `reports/repair-plan.md` | 带来源锚点和停止条件的修复计划 |
140
+ | `reports/final-consistency-report.md` | 最终一致性结论与残余风险 |
141
+ | `reports/FINAL_RESULT.json` | 机器可读的最终状态 |
142
+ | `logs/trace/` | Intake、委派、修改和验证证据 |
143
+
144
+ 最终状态只使用 `PASS`、`PARTIAL`、`BLOCKED` 或 `FAIL`。`PASS` 表示证据链和验证均满足要求,并不只是“测试刚好通过”。
145
+
146
+ ### 常见问题
147
+
148
+ - **找不到 Skill/Subagent**:重启 Coding Agent,并使用 `--dry-run` 检查安装目标。
149
+ - **只想当前仓库使用**:Claude Code、OpenCode、MiMo Code 安装时增加 `--scope project`。
150
+ - **项目没有 OpenSpec**:仍可使用设计文档、API、Schema、README 或产品需求作为权威设计源。
151
+ - **缺少验证工具**:记录缺失的命令和环境原因,最终状态应为 `BLOCKED` 或 `PARTIAL`,不要伪造成功。
152
+ - **测试通过是否等于一致**:不等于。还必须确认需求、分支、状态迁移、副作用及集成流程符合设计。
153
+
62
154
  ### 双 npm 包发布
63
155
 
64
156
  每次发布必须以相同版本、相同内容发布两个包名:
@@ -69,7 +161,7 @@ dic-workflow-kit install
69
161
  `package.json` 是唯一版本源。版本脚本会同步 Codex 插件清单、工作流脚本、全部 Skills、全部 Subagents 和中英文 README:
70
162
 
71
163
  ```text
72
- npm run release:set-version -- 1.1.0
164
+ npm run release:set-version -- 1.1.1
73
165
  npm run release:plan
74
166
  npm run release:dual:dry-run
75
167
  npm run release:dual
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: code-repairer
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Implement approved repair slices while preserving contracts, minimizing blast radius, and avoiding unrelated refactors.
5
5
  mode: subagent
6
6
  ---
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: contract-oracle
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Convert source requirements, OpenSpec scenarios, and feedback hypotheses into source-confirmed implementation obligations.
5
5
  mode: subagent
6
6
  ---
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: final-reviewer
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Perform the final consistency gate across source coverage, protected paths, validation evidence, residual risks, changed files, and output artifacts.
5
5
  mode: subagent
6
6
  ---
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: flow-auditor
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Audit business and use-case flow completeness, including lifecycle, branches, state transitions, side effects, integration paths, and failure handling.
5
5
  mode: subagent
6
6
  ---
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: impl-inspector
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Inspect implementation against source-confirmed obligations without editing files.
5
5
  mode: subagent
6
6
  ---
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: profile-builder
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Build a normalized project profile from repository evidence so downstream agents stop guessing paths, tools, and source hierarchy.
5
5
  mode: subagent
6
6
  ---
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: repair-planner
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Create small, source-backed repair slices with target files, validation commands, stop conditions, and fallback plans.
5
5
  mode: subagent
6
6
  ---
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: spec-reader
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Read authoritative design, OpenSpec, API, schema, README, and configuration sources and produce a source-backed requirement brief.
5
5
  mode: subagent
6
6
  ---
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: validation-runner
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Discover, run, and summarize project validation commands using evaluator-readable evidence.
5
5
  mode: subagent
6
6
  ---
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "dic-workflow-kit",
3
- "version": "1.1.0",
3
+ "version": "1.1.1",
4
4
  "description": "Install DIC Workflow Kit Skills and Subagents for Codex, Claude Code, OpenCode, and MiMo Code.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -13,6 +13,7 @@
13
13
  "dist/",
14
14
  "schemas/",
15
15
  "skills/",
16
+ "CHANGELOG.md",
16
17
  "INSTRUCTION.md",
17
18
  "README.md"
18
19
  ],
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: knowledge-bdd
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Derive Given-When-Then acceptance scenarios from confirmed design rules and flow contracts.
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: knowledge-openspec
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: OpenSpec knowledge pack for proposals, specs, scenarios, tasks, changes, archived capabilities, validation, and design-to-implementation mapping.
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: knowledge-repair-distill
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Generic repair convergence guidance, gap taxonomy, model steering hints, and validation gates for design-implementation consistency work.
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: workflow-core
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Core Design-Implementation Consistency workflow contract, evidence model, handoff rules, and final output expectations.
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: workflow-intake
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Discover authoritative design sources, implementation roots, test roots, protected paths, validation commands, and adapter hints.
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: workflow-profile
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Build a normalized project profile for design-implementation consistency work without hardcoding a repository or technology stack.
5
5
  ---
6
6
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: workflow-repair
3
- version: 1.1.0
3
+ version: 1.1.1
4
4
  description: Guide source-backed implementation inspection, repair planning, code repair, validation loops, and final consistency evidence.
5
5
  ---
6
6