@miniidealab/openlogos 0.9.11 → 0.9.12

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,7 +1,7 @@
1
1
  {
2
2
  "name": "openlogos",
3
3
  "description": "OpenLogos methodology plugin — structured AI-driven development with Why → What → How progression",
4
- "version": "0.9.11",
4
+ "version": "0.9.12",
5
5
  "author": {
6
6
  "name": "MiniIdeaLab",
7
7
  "url": "https://github.com/miniidealab"
@@ -94,23 +94,67 @@ Automatically break down the task checklist based on the change type and impact
94
94
  # Implementation Tasks
95
95
 
96
96
  ## Phase 1: Document Changes
97
- - [ ] Update acceptance criteria for S0x in requirement documents
98
- - [ ] Add/modify scenario in the scenario overview table
97
+ - [ ] Output delta file to `deltas/prd/` — Update acceptance criteria for S0x in requirement documents
98
+ - [ ] Output delta file to `deltas/prd/` — Add/modify scenario in the scenario overview table
99
99
 
100
100
  ## Phase 2: Design Changes
101
- - [ ] Update interaction design for S0x in functional specs
102
- - [ ] Update prototypes
101
+ - [ ] Output delta file to `deltas/prd/` — Update interaction design for S0x in functional specs
102
+ - [ ] Output delta file to `deltas/prd/` — Update prototypes
103
103
 
104
104
  ## Phase 3: Technical Changes
105
- - [ ] Update sequence diagram for S0x
106
- - [ ] Update API YAML
105
+ - [ ] Output delta file to `deltas/prd/` — Update sequence diagram for S0x
106
+ - [ ] Output delta file to `deltas/api/` — Update API YAML
107
107
  - [ ] **Validate API YAML** — all files in `logos/resources/api/` must be valid YAML and valid OpenAPI 3.x (all `description`/`summary` values containing `:` or special chars must be double-quoted)
108
- - [ ] Update DB DDL
109
- - [ ] Update orchestration test cases
110
- - [ ] Implement code changes
108
+ - [ ] Output delta file to `deltas/database/` — Update DB DDL
109
+ - [ ] Output delta file to `deltas/scenario/` — Update orchestration test cases
110
+ - [ ] Implement code changes (modify `src/` directly — no delta needed)
111
111
  ```
112
112
 
113
- ### Step 6: Guide Follow-up Actions (Chain-driven)
113
+ ### Step 6: Output Delta Files
114
+
115
+ **When to trigger**: After tasks.md is filled in and the user has confirmed the proposal, produce delta files item by item per the task checklist.
116
+
117
+ #### Directory Mapping
118
+
119
+ Delta files are written to the corresponding subdirectory under `logos/changes/<slug>/deltas/`, mirroring the `logos/resources/` structure:
120
+
121
+ | Target main document directory | Delta subdirectory |
122
+ |---|---|
123
+ | `logos/resources/prd/` | `deltas/prd/` |
124
+ | `logos/resources/api/` | `deltas/api/` |
125
+ | `logos/resources/database/` | `deltas/database/` |
126
+ | `logos/resources/scenario/` | `deltas/scenario/` |
127
+
128
+ Code implementation (`src/`, `test/`) does **not** produce delta files — modify source files directly.
129
+
130
+ #### File Naming
131
+
132
+ Use the **same name** as the target main document (including subdirectory levels). For example:
133
+ - Target: `logos/resources/api/core-api.yaml` → delta: `deltas/api/core-api.yaml`
134
+ - Target: `logos/resources/prd/1-product-requirements/core-01-requirements.md` → delta: `deltas/prd/1-product-requirements/core-01-requirements.md`
135
+
136
+ #### File Format
137
+
138
+ Each delta file uses `ADDED / MODIFIED / REMOVED` markers, with each block corresponding to one section in the main document:
139
+
140
+ ```markdown
141
+ ## ADDED — [New section title]
142
+ [Complete content to add]
143
+
144
+ ## MODIFIED — [Modified section title]
145
+ [Complete updated content — replaces the same-named section in the main document during merge]
146
+
147
+ ## REMOVED — [Deleted section title]
148
+ [Explain the reason for deletion — the same-named section will be removed from the main document during merge]
149
+ ```
150
+
151
+ #### Behavioral Rules
152
+
153
+ - After completing each delta file, immediately update the corresponding item in `tasks.md` from `[ ]` to `[x]`
154
+ - **Do NOT directly modify documents under `logos/resources/`** — all spec changes must go through delta files and be merged via `openlogos merge`
155
+ - After all deltas are produced, remind the user to explicitly authorize running `openlogos merge <slug>`
156
+
157
+ ### Step 7: Guide Follow-up Actions (Chain-driven)
114
158
 
115
159
  Provide a ready-to-use prompt that allows the user to kick off chain execution of all tasks with a single command:
116
160
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@miniidealab/openlogos",
3
- "version": "0.9.11",
3
+ "version": "0.9.12",
4
4
  "description": "CLI tool for the OpenLogos software engineering methodology",
5
5
  "type": "module",
6
6
  "bin": {
@@ -91,23 +91,67 @@
91
91
  # 实现任务
92
92
 
93
93
  ## Phase 1: 文档变更
94
- - [ ] 更新需求文档中 S0x 的验收条件
95
- - [ ] 在场景总览表中新增/修改场景
94
+ - [ ] 产出 delta 文件到 `deltas/prd/` — 更新需求文档中 S0x 的验收条件
95
+ - [ ] 产出 delta 文件到 `deltas/prd/` — 在场景总览表中新增/修改场景
96
96
 
97
97
  ## Phase 2: 设计变更
98
- - [ ] 更新功能规格中 S0x 的交互设计
99
- - [ ] 更新原型
98
+ - [ ] 产出 delta 文件到 `deltas/prd/` — 更新功能规格中 S0x 的交互设计
99
+ - [ ] 产出 delta 文件到 `deltas/prd/` — 更新原型
100
100
 
101
101
  ## Phase 3: 技术变更
102
- - [ ] 更新 S0x 的时序图
103
- - [ ] 更新 API YAML
102
+ - [ ] 产出 delta 文件到 `deltas/prd/` — 更新 S0x 的时序图
103
+ - [ ] 产出 delta 文件到 `deltas/api/` — 更新 API YAML
104
104
  - [ ] **验证 API YAML** — `logos/resources/api/` 下所有文件必须为有效 YAML 且符合 OpenAPI 3.x 规范(所有包含 `:` 或特殊字符的 `description`/`summary` 值必须用双引号包裹)
105
- - [ ] 更新 DB DDL
106
- - [ ] 更新编排测试用例
107
- - [ ] 实现代码变更
105
+ - [ ] 产出 delta 文件到 `deltas/database/` — 更新 DB DDL
106
+ - [ ] 产出 delta 文件到 `deltas/scenario/` — 更新编排测试用例
107
+ - [ ] 实现代码变更(直接修改 `src/`,无需 delta)
108
108
  ```
109
109
 
110
- ### Step 6: 引导后续操作(链式驱动)
110
+ ### Step 6: 产出 Delta 文件
111
+
112
+ **触发时机**:tasks.md 填写完成、用户确认提案后,按任务清单逐项产出 delta 文件。
113
+
114
+ #### 目录映射
115
+
116
+ Delta 文件写入 `logos/changes/<slug>/deltas/` 下对应子目录,与 `logos/resources/` 一一对应:
117
+
118
+ | 目标主文档目录 | Delta 子目录 |
119
+ |---|---|
120
+ | `logos/resources/prd/` | `deltas/prd/` |
121
+ | `logos/resources/api/` | `deltas/api/` |
122
+ | `logos/resources/database/` | `deltas/database/` |
123
+ | `logos/resources/scenario/` | `deltas/scenario/` |
124
+
125
+ 代码实现(`src/`、`test/`)**不产出 delta**,直接修改源文件。
126
+
127
+ #### 文件命名
128
+
129
+ 与目标主文档**同名**(含子目录层级)。例如:
130
+ - 目标:`logos/resources/api/core-api.yaml` → delta:`deltas/api/core-api.yaml`
131
+ - 目标:`logos/resources/prd/1-product-requirements/core-01-requirements.md` → delta:`deltas/prd/1-product-requirements/core-01-requirements.md`
132
+
133
+ #### 文件格式
134
+
135
+ 每个 delta 文件使用 `ADDED / MODIFIED / REMOVED` 标记,每个标记块对应主文档中的一个章节:
136
+
137
+ ```markdown
138
+ ## ADDED — [新增章节标题]
139
+ [新增的完整内容]
140
+
141
+ ## MODIFIED — [修改章节标题]
142
+ [修改后的完整内容,merge 时替换主文档中同名章节]
143
+
144
+ ## REMOVED — [删除章节标题]
145
+ [说明删除原因,merge 时删除主文档中同名章节]
146
+ ```
147
+
148
+ #### 行为规范
149
+
150
+ - 每完成一个 delta 文件,立即将 `tasks.md` 中对应条目从 `[ ]` 更新为 `[x]`
151
+ - **禁止直接修改 `logos/resources/` 下的主文档**——所有规格变更必须通过 delta 文件,由 `openlogos merge` 统一合并
152
+ - 全部 delta 产出完成后,提醒用户明确授权运行 `openlogos merge <slug>`
153
+
154
+ ### Step 7: 引导后续操作(链式驱动)
111
155
 
112
156
  提供一条可直接执行的提示词,让用户一句话启动全部任务的链式执行:
113
157