mspec-cli 4.0.11__tar.gz → 4.0.12__tar.gz
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.
- {mspec_cli-4.0.11/src/mspec_cli.egg-info → mspec_cli-4.0.12}/PKG-INFO +1 -1
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/pyproject.toml +1 -1
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/__init__.py +1 -1
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/templates/config.yaml +8 -5
- {mspec_cli-4.0.11 → mspec_cli-4.0.12/src/mspec_cli.egg-info}/PKG-INFO +1 -1
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/LICENSE +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/MANIFEST.in +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/README.md +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/setup.cfg +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/__main__.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/cli.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/commands/__init__.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/commands/doctor.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/commands/init.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/commands/update.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/core/__init__.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/core/config.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/core/openspec_manager.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/core/template.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/templates/design-issue-taxonomy.md +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/templates/design-issues.md +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/templates/requirement-issue-taxonomy.md +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/templates/requirement-issues.md +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/utils/__init__.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec/utils/console.py +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec_cli.egg-info/SOURCES.txt +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec_cli.egg-info/dependency_links.txt +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec_cli.egg-info/entry_points.txt +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec_cli.egg-info/requires.txt +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/src/mspec_cli.egg-info/top_level.txt +0 -0
- {mspec_cli-4.0.11 → mspec_cli-4.0.12}/tests/test_init.py +0 -0
|
@@ -56,11 +56,14 @@ context: |
|
|
|
56
56
|
步骤 1: 读取 openspec/templates/design-issue-taxonomy.md
|
|
57
57
|
步骤 2: 按 7 个维度分析 design.md 的不确定性
|
|
58
58
|
步骤 3: 创建 spec/design-issues.md
|
|
59
|
-
步骤 4:
|
|
60
|
-
|
|
61
|
-
-
|
|
62
|
-
|
|
63
|
-
-
|
|
59
|
+
步骤 4: 【强制用户确认——无论是否发现问题都必须执行】
|
|
60
|
+
使用 AskUserQuestion 工具，将分析结果呈现给用户并请求确认：
|
|
61
|
+
- 如果发现 High/Medium 问题：将所有问题组织为编号列表，一次性展示：
|
|
62
|
+
格式："需要确认 N 个设计问题，请一并回答：\n1. [问题]\n 选项：A) ... B) ...\n2. ..."
|
|
63
|
+
- 如果未发现 High/Medium 问题：仍须展示分析摘要并确认：
|
|
64
|
+
格式："设计分析完成，未发现高优先级问题。主要设计决策摘要如下：\n[列出关键决策]\n请确认以上设计，或提出任何顾虑/补充："
|
|
65
|
+
- 等待用户回答，不得跳过此步骤
|
|
66
|
+
- 收到回答后，将用户意见同步到 design-issues.md
|
|
64
67
|
步骤 5: 根据澄清结果更新 design.md
|
|
65
68
|
步骤 6: 更新状态为 clarified
|
|
66
69
|
```
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|