@s_s/harmonia 1.2.0 → 1.4.0

package/workflows/dev/schemas/prd.requirements.json

@@ -2,24 +2,25 @@
     "jsonFields": [
         {
             "field": "features",
-            "required": { "small": true, "medium": true, "large": true },
+            "required": true,
             "type": "array",
             "minItems": 1
         },
         {
             "field": "constraints",
-            "required": { "small": false, "medium": true, "large": true },
+            "required": true,
             "type": "array"
         },
         {
             "field": "priorities",
-            "required": { "small": false, "medium": true, "large": true },
+            "required": true,
             "type": "object"
         },
         {
             "field": "scope",
-            "required": { "small": true, "medium": true, "large": true },
+            "required": true,
             "type": "string"
         }
-    ]
+    ],
+    "guidance": "将用户原始需求结构化为 JSON 格式。只提取需求信息（功能列表、约束、优先级、范围），不做技术分析或方案设计。"
 }

package/workflows/dev/schemas/prototype.json

@@ -1,4 +1,8 @@
 {
-    "htmlTags": ["html", "body"],
-    "minLength": 200
+    "htmlTags": [
+        "html",
+        "body"
+    ],
+    "minLength": 200,
+    "guidance": "高保真 HTML 原型，展示页面布局、交互流程和状态反馈。必须是完整的可在浏览器中打开的 HTML 文件。"
 }

package/workflows/dev/schemas/task-breakdown.coarse.json

@@ -2,14 +2,15 @@
     "jsonFields": [
         {
             "field": "tasks",
-            "required": { "small": true, "medium": true, "large": true },
+            "required": true,
             "type": "array",
             "minItems": 1
         },
         {
             "field": "estimatedTotal",
-            "required": { "small": false, "medium": true, "large": true },
+            "required": true,
             "type": "string"
         }
-    ]
+    ],
+    "guidance": "按功能模块粗粒度拆分任务，标注预估工作量。聚焦任务划分的合理性，不需要细化到具体实现步骤。"
 }

package/workflows/dev/schemas/task-breakdown.dependencies.json

@@ -2,19 +2,20 @@
     "jsonFields": [
         {
             "field": "dependencies",
-            "required": { "small": true, "medium": true, "large": true },
+            "required": true,
             "type": "array"
         },
         {
             "field": "executionOrder",
-            "required": { "small": false, "medium": true, "large": true },
+            "required": true,
             "type": "array",
             "minItems": 1
         },
         {
             "field": "parallelGroups",
-            "required": { "small": false, "medium": false, "large": true },
+            "required": true,
             "type": "array"
         }
-    ]
+    ],
+    "guidance": "分析任务间的依赖关系，确定执行顺序和可并行的任务组。输出结构化 JSON。"
 }

package/workflows/dev/schemas/task-breakdown.detailed.json

@@ -2,9 +2,14 @@
     "sections": [
         {
             "heading": "## 任务列表",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Task List", "## 任务清单", "## Tasks"]
+            "required": true,
+            "aliases": [
+                "## Task List",
+                "## 任务清单",
+                "## Tasks"
+            ]
         }
     ],
-    "minLength": 80
+    "minLength": 80,
+    "guidance": "将粗粒度任务细化为具体的开发任务，每个任务应包含明确的输入、输出和完成标准。"
 }

package/workflows/dev/schemas/task-breakdown.final.json

@@ -2,9 +2,14 @@
     "sections": [
         {
             "heading": "## 任务列表",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Task List", "## 任务清单", "## Tasks"]
+            "required": true,
+            "aliases": [
+                "## Task List",
+                "## 任务清单",
+                "## Tasks"
+            ]
         }
     ],
-    "minLength": 100
+    "minLength": 100,
+    "guidance": "任务拆解最终版，整合依赖关系和执行顺序。每个任务需标注是否可并行、依赖哪些前置任务。"
 }

package/workflows/dev/schemas/task-breakdown.json

@@ -2,9 +2,14 @@
     "sections": [
         {
             "heading": "## 任务列表",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Task List", "## 任务清单", "## Tasks"]
+            "required": true,
+            "aliases": [
+                "## Task List",
+                "## 任务清单",
+                "## Tasks"
+            ]
         }
     ],
-    "minLength": 100
+    "minLength": 100,
+    "guidance": "任务拆解文档，将技术方案拆分为可执行的开发任务。每个任务要具体到开发者能直接开始编码。"
 }

package/workflows/dev/schemas/tech-design.analysis.json

@@ -2,24 +2,25 @@
     "jsonFields": [
         {
             "field": "currentArchitecture",
-            "required": { "small": false, "medium": true, "large": true },
+            "required": true,
             "type": "object"
         },
         {
             "field": "constraints",
-            "required": { "small": true, "medium": true, "large": true },
+            "required": true,
             "type": "array"
         },
         {
             "field": "proposals",
-            "required": { "small": true, "medium": true, "large": true },
+            "required": true,
             "type": "array",
             "minItems": 1
         },
         {
             "field": "recommendation",
-            "required": { "small": true, "medium": true, "large": true },
+            "required": true,
             "type": "string"
         }
-    ]
+    ],
+    "guidance": "分析现有架构和技术约束，提出可行方案并给出推荐。输出结构化 JSON，聚焦技术可行性分析。"
 }

package/workflows/dev/schemas/tech-design.draft.json

@@ -2,14 +2,23 @@
     "sections": [
         {
             "heading": "## 架构概述",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Architecture Overview", "## 系统架构", "## 架构设计"]
+            "required": true,
+            "aliases": [
+                "## Architecture Overview",
+                "## 系统架构",
+                "## 架构设计"
+            ]
         },
         {
             "heading": "## 技术选型",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Technology Stack", "## 技术栈", "## Tech Stack"]
+            "required": true,
+            "aliases": [
+                "## Technology Stack",
+                "## 技术栈",
+                "## Tech Stack"
+            ]
         }
     ],
-    "minLength": 150
+    "minLength": 150,
+    "guidance": "技术方案草稿，聚焦架构概述和技术选型两个核心章节。"
 }

package/workflows/dev/schemas/tech-design.final.json

@@ -2,29 +2,55 @@
     "sections": [
         {
             "heading": "## 架构概述",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Architecture Overview", "## 系统架构", "## 架构设计"]
+            "required": true,
+            "aliases": [
+                "## Architecture Overview",
+                "## 系统架构",
+                "## 架构设计"
+            ]
         },
         {
             "heading": "## 技术选型",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Technology Stack", "## 技术栈", "## Tech Stack"]
+            "required": true,
+            "aliases": [
+                "## Technology Stack",
+                "## 技术栈",
+                "## Tech Stack"
+            ]
         },
         {
             "heading": "## 模块设计",
-            "required": { "small": false, "medium": true, "large": true },
-            "aliases": ["## Module Design", "## 组件设计", "## 模块划分"]
+            "required": true,
+            "aliases": [
+                "## Module Design",
+                "## 组件设计",
+                "## 模块划分"
+            ]
         },
         {
-            "heading": "## 接口设计",
-            "required": { "small": false, "medium": true, "large": true },
-            "aliases": ["## Interface Design", "## API 设计", "## 接口定义"]
+            "heading": "## 架构决策",
+            "required": true,
+            "aliases": [
+                "## Architecture Decisions",
+                "## 设计决策",
+                "## 技术决策"
+            ]
         },
         {
-            "heading": "## 数据模型",
-            "required": { "small": false, "medium": false, "large": true },
-            "aliases": ["## Data Model", "## 数据设计", "## 数据结构"]
+            "heading": "## 风险评估",
+            "required": true,
+            "aliases": [
+                "## Risk Assessment",
+                "## 技术风险",
+                "## 风险分析"
+            ]
+        },
+        {
+            "heading": "## UML 建模",
+            "required": true,
+            "aliases": ["## UML", "## UML 图", "## 架构建模"]
         }
     ],
-    "minLength": 200
+    "minLength": 200,
+    "guidance": "技术方案最终版，需包含所有必需章节。确保架构决策有理有据，模块设计清晰可执行，风险评估完整。"
 }

package/workflows/dev/schemas/tech-design.json

@@ -2,29 +2,50 @@
     "sections": [
         {
             "heading": "## 架构概述",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Architecture Overview", "## 系统架构", "## 架构设计"]
+            "required": true,
+            "aliases": [
+                "## Architecture Overview",
+                "## 系统架构",
+                "## 架构设计"
+            ]
         },
         {
             "heading": "## 技术选型",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Technology Stack", "## 技术栈", "## Tech Stack"]
+            "required": true,
+            "aliases": [
+                "## Technology Stack",
+                "## 技术栈",
+                "## Tech Stack"
+            ]
         },
         {
             "heading": "## 模块设计",
-            "required": { "small": false, "medium": true, "large": true },
-            "aliases": ["## Module Design", "## 组件设计", "## 模块划分"]
+            "required": true,
+            "aliases": [
+                "## Module Design",
+                "## 组件设计",
+                "## 模块划分"
+            ]
         },
         {
-            "heading": "## 接口设计",
-            "required": { "small": false, "medium": true, "large": true },
-            "aliases": ["## Interface Design", "## API 设计", "## 接口定义"]
+            "heading": "## 架构决策",
+            "required": true,
+            "aliases": [
+                "## Architecture Decisions",
+                "## 设计决策",
+                "## 技术决策"
+            ]
         },
         {
-            "heading": "## 数据模型",
-            "required": { "small": false, "medium": false, "large": true },
-            "aliases": ["## Data Model", "## 数据设计", "## 数据结构"]
+            "heading": "## 风险评估",
+            "required": true,
+            "aliases": [
+                "## Risk Assessment",
+                "## 技术风险",
+                "## 风险分析"
+            ]
         }
     ],
-    "minLength": 200
+    "minLength": 200,
+    "guidance": "技术方案描述如何实现需求（怎么做），包括架构概述、技术选型、模块设计、架构决策及其依据、风险评估。接口设计和数据模型已拆为独立产出（api-design、data-model），此处聚焦架构层面。"
 }

package/workflows/dev/schemas/tech-design.research.json

@@ -0,0 +1,21 @@
+{
+    "jsonFields": [
+        {
+            "field": "items",
+            "required": true,
+            "type": "array",
+            "minItems": 1
+        },
+        {
+            "field": "risks",
+            "required": true,
+            "type": "array"
+        },
+        {
+            "field": "conclusion",
+            "required": true,
+            "type": "string"
+        }
+    ],
+    "guidance": "技术预研报告：三方对接/外部依赖的可行性验证、风险评估、替代方案。每项预研包含结论和依据。"
+}

package/workflows/dev/schemas/test-plan.json

@@ -2,19 +2,29 @@
     "sections": [
         {
             "heading": "## 测试范围",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Test Scope", "## 测试目标"]
+            "required": true,
+            "aliases": [
+                "## Test Scope",
+                "## 测试目标"
+            ]
         },
         {
             "heading": "## 测试策略",
-            "required": { "small": false, "medium": true, "large": true },
-            "aliases": ["## Test Strategy", "## 测试方法"]
+            "required": true,
+            "aliases": [
+                "## Test Strategy",
+                "## 测试方法"
+            ]
         },
         {
             "heading": "## 测试用例",
-            "required": { "small": false, "medium": true, "large": true },
-            "aliases": ["## Test Cases", "## 用例列表"]
+            "required": true,
+            "aliases": [
+                "## Test Cases",
+                "## 用例列表"
+            ]
         }
     ],
-    "minLength": 100
+    "minLength": 100,
+    "guidance": "测试计划文档，基于 user-stories 验收标准制定测试策略和用例。覆盖功能测试（参照 prototype 交互流程）和内部模块 API 测试（参照 api-design 方法签名）。"
 }

package/workflows/dev/schemas/test-report.json

@@ -2,24 +2,41 @@
     "sections": [
         {
             "heading": "## 测试范围",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Test Scope", "## 测试目标", "## 测试概述"]
+            "required": true,
+            "aliases": [
+                "## Test Scope",
+                "## 测试目标",
+                "## 测试概述"
+            ]
         },
         {
             "heading": "## 测试结果",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## Test Results", "## 用例结果", "## 执行结果"]
+            "required": true,
+            "aliases": [
+                "## Test Results",
+                "## 用例结果",
+                "## 执行结果"
+            ]
         },
         {
             "heading": "## 问题列表",
-            "required": { "small": false, "medium": true, "large": true },
-            "aliases": ["## Issues", "## 缺陷列表", "## 问题与缺陷"]
+            "required": true,
+            "aliases": [
+                "## Issues",
+                "## 缺陷列表",
+                "## 问题与缺陷"
+            ]
         },
         {
             "heading": "## 覆盖率",
-            "required": { "small": false, "medium": false, "large": true },
-            "aliases": ["## Coverage", "## 测试覆盖率", "## 代码覆盖率"]
+            "required": true,
+            "aliases": [
+                "## Coverage",
+                "## 测试覆盖率",
+                "## 代码覆盖率"
+            ]
         }
     ],
-    "minLength": 100
+    "minLength": 100,
+    "guidance": "测试报告，如实记录测试执行结果：通过/失败/跳过统计，失败用例的详细信息和复现步骤。"
 }

package/workflows/dev/schemas/user-stories.json

@@ -2,9 +2,13 @@
     "sections": [
         {
             "heading": "## 用户故事",
-            "required": { "small": true, "medium": true, "large": true },
-            "aliases": ["## User Stories", "## 用户场景"]
+            "required": true,
+            "aliases": [
+                "## User Stories",
+                "## 用户场景"
+            ]
         }
     ],
-    "minLength": 100
+    "minLength": 100,
+    "guidance": "基于 prd 和已确认的 prototype 交互设计，从用户视角描述功能需求。每个故事包含角色、目标和验收标准。格式：作为<角色>，我想<目标>，以便<价值>。"
 }

package/workflows/dev/tools/index.js

@@ -0,0 +1,23 @@
+/**
+ * Dev workflow — action registration.
+ *
+ * This module exports a registerActions function called by the plugin loader.
+ * Actions are invoked by beforeDispatch/afterComplete hooks defined in workflow.json
+ * node definitions.
+ *
+ * Currently no custom actions are registered for the dev workflow.
+ */
+
+/**
+ * Register dev workflow actions.
+ *
+ * @param api - Registration API provided by the plugin loader
+ * @param api.register - Function to register an action by name and handler
+ */
+export function registerActions(_api) {
+    // No custom actions yet.
+    // Example:
+    //   api.register('check-dependencies', async (ctx) => {
+    //       return { inject: ['Dependencies are up to date.'] };
+    //   });
+}