mspec-cli 5.1.0__tar.gz → 5.1.1__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-5.1.0/src/mspec_cli.egg-info → mspec_cli-5.1.1}/PKG-INFO +1 -1
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/pyproject.toml +1 -1
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/__init__.py +1 -1
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/config.yaml +22 -11
- {mspec_cli-5.1.0 → mspec_cli-5.1.1/src/mspec_cli.egg-info}/PKG-INFO +1 -1
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/LICENSE +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/MANIFEST.in +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/README.md +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/setup.cfg +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/__main__.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/cli.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/commands/__init__.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/commands/doctor.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/commands/init.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/commands/update.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/core/__init__.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/core/config.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/core/openspec_manager.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/core/template.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/evolution/adr.md +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/evolution/glossary.md +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/evolution/risk-map.md +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/issues/design-issues.md +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/issues/requirement-issues.md +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/issues/retrospective-notes.md +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/taxonomy/design-issue-taxonomy.md +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/taxonomy/requirement-issue-taxonomy.md +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/utils/__init__.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/utils/console.py +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec_cli.egg-info/SOURCES.txt +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec_cli.egg-info/dependency_links.txt +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec_cli.egg-info/entry_points.txt +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec_cli.egg-info/requires.txt +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec_cli.egg-info/top_level.txt +0 -0
- {mspec_cli-5.1.0 → mspec_cli-5.1.1}/tests/test_init.py +0 -0
|
@@ -35,10 +35,16 @@ context: |
|
|
|
35
35
|
步骤 2: 分析需求,识别功能点(Capabilities)
|
|
36
36
|
步骤 3: 按 6 个维度检查每个功能点的问题
|
|
37
37
|
步骤 4: 创建 spec/requirement-issues.md,填充发现问题
|
|
38
|
-
步骤 5:
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
-
|
|
38
|
+
步骤 5: 启动批量澄清(一次性提问 - MUST 使用 AskUserQuestion 工具)
|
|
39
|
+
⚠️ 禁止直接文本提问,必须使用 AskUserQuestion 工具调用
|
|
40
|
+
|
|
41
|
+
- 问题数 ≤ 6:全展开界面
|
|
42
|
+
- 问题数 > 6:单题+进度界面
|
|
43
|
+
|
|
44
|
+
AskUserQuestion 参数:
|
|
45
|
+
- question: "🔍 需求澄清 - 共N个问题(High: H, Medium: M)"
|
|
46
|
+
- 每个问题作为一个 option(header: "[序号/N] 问题ID 严重程度", description: 问题描述)
|
|
47
|
+
- 等待用户一次性选择所有答案后统一提交
|
|
42
48
|
- 收到完整回答后,统一同步到 requirement-issues.md
|
|
43
49
|
步骤 6: 确认所有 High 问题已澄清后,更新状态为 clarified
|
|
44
50
|
```
|
|
@@ -56,13 +62,18 @@ context: |
|
|
|
56
62
|
步骤 1: 读取 openspec/templates/taxonomy/design-issue-taxonomy.md
|
|
57
63
|
步骤 2: 按 7 个维度分析 design.md 的不确定性
|
|
58
64
|
步骤 3: 创建 spec/design-issues.md
|
|
59
|
-
步骤 4:
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
-
|
|
64
|
-
|
|
65
|
-
|
|
65
|
+
步骤 4: 【强制用户确认 - MUST 使用 AskUserQuestion 工具】
|
|
66
|
+
⚠️ 禁止直接文本提问,必须使用 AskUserQuestion 工具调用
|
|
67
|
+
|
|
68
|
+
使用 AskUserQuestion 呈现分析结果:
|
|
69
|
+
- 如果发现 High/Medium 问题:
|
|
70
|
+
* question: "🔧 设计澄清 - 共N个问题(High: H, Medium: M)"
|
|
71
|
+
* 问题数 ≤ 6:全展开界面,问题数 > 6:单题+进度界面
|
|
72
|
+
* 每个问题作为一个 option(header: "[序号/N] 问题ID 严重程度")
|
|
73
|
+
- 如果未发现 High/Medium 问题:
|
|
74
|
+
* question: "🔧 设计分析确认"
|
|
75
|
+
* 展示分析摘要,确认设计决策
|
|
76
|
+
- 等待用户一次性回答所有问题
|
|
66
77
|
- 收到回答后,将用户意见同步到 design-issues.md
|
|
67
78
|
步骤 5: 根据澄清结果更新 design.md
|
|
68
79
|
步骤 6: 更新状态为 clarified
|
|
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
|
{mspec_cli-5.1.0 → mspec_cli-5.1.1}/src/mspec/templates/taxonomy/requirement-issue-taxonomy.md
RENAMED
|
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
|