mcp-probe-kit 3.0.9 → 3.0.11

package/build/tools/start_feature.js

@@ -1,3 +1,5 @@
+import * as fs from "node:fs";
+import * as path from "node:path";
 import { parseArgs, getString, getNumber } from "../utils/parseArgs.js";
 import { okStructured } from "../lib/response.js";
 import { renderOrchestrationHeader } from "../lib/orchestration-guidance.js";
@@ -62,12 +64,15 @@ const PROMPT_TEMPLATE = `# 🚀 新功能开发编排（委托式）
 
 ## ✅ 执行计划（按顺序）
 
-### 0) 项目上下文（如缺失）
-**检查**: \`{docs_dir}/project-context.md\`  
-**缺失则调用**: \`init_project_context\`
-\`\`\`json
-{ "docs_dir": "{docs_dir}" }
-\`\`\`
+### 0) 项目上下文（如缺失）
+**检查**:
+- \`{docs_dir}/project-context.md\`
+- \`{docs_dir}/graph-insights/latest.md\`
+- \`{docs_dir}/graph-insights/latest.json\`
+**缺失则调用**: \`init_project_context\`
+\`\`\`json
+{ "docs_dir": "{docs_dir}", "project_root": "{project_root}" }
+\`\`\`
 
 ### 1) 生成功能规格
 **调用**: \`add_feature\`
@@ -95,11 +100,12 @@ const PROMPT_TEMPLATE = `# 🚀 新功能开发编排（委托式）
 
 ---
 
-## ✅ 输出汇总（执行完成后）
-1. 规格文档位置: \`{docs_dir}/specs/{feature_name}/\`
-2. 估算结果: 故事点 + 时间区间
-3. 主要风险（如有）
-4. 下一步: 按 tasks.md 开始开发
+## ✅ 输出汇总（执行完成后）
+1. 规格文档位置: \`{docs_dir}/specs/{feature_name}/\`
+2. 图谱入口: \`{docs_dir}/graph-insights/latest.md\`
+3. 估算结果: 故事点 + 时间区间
+4. 主要风险（如有）
+5. 下一步: 按 tasks.md 开始开发
 
 ---
 
@@ -186,6 +192,7 @@ export async function startFeature(args, context) {
                 feature_name: ["name", "feature", "功能名", "功能名称"],
                 description: ["desc", "requirement", "描述", "需求"],
                 docs_dir: ["dir", "output", "目录", "文档目录"],
+                project_root: ["projectRoot", "project_path", "projectPath", "root", "project_root", "项目路径", "项目根目录"],
                 template_profile: ["profile", "template_profile", "模板档位", "模板模式"],
                 requirements_mode: ["mode", "requirements_mode", "loop", "需求模式"],
                 loop_max_rounds: ["max_rounds", "rounds", "最大轮次"],
@@ -196,6 +203,7 @@ export async function startFeature(args, context) {
         let featureName = getString(parsedArgs.feature_name);
         let description = getString(parsedArgs.description);
         const docsDir = getString(parsedArgs.docs_dir) || "docs";
+        const projectRoot = getString(parsedArgs.project_root);
         const templateProfile = getString(parsedArgs.template_profile) || "auto";
         const requirementsMode = getString(parsedArgs.requirements_mode) || "steady";
         const maxRounds = getNumber(parsedArgs.loop_max_rounds, 2);
@@ -227,30 +235,47 @@ export async function startFeature(args, context) {
                 "- JSON格式：{\"feature_name\": \"user-auth\", \"description\": \"用户认证功能\"}");
         }
         throwIfAborted(context?.signal, "start_feature 已取消");
-        await reportToolProgress(context, 55, "start_feature: 获取代码图谱上下文");
+        await reportToolProgress(context, 55, "start_feature: 刷新图谱并收敛需求范围");
+        const graphDocs = {
+            latestMarkdownPath: `${docsDir}/graph-insights/latest.md`,
+            latestJsonPath: `${docsDir}/graph-insights/latest.json`,
+        };
+        const resolvedProjectRoot = path.resolve(projectRoot || process.cwd());
+        const bootstrapState = {
+            projectContextExists: fs.existsSync(path.join(resolvedProjectRoot, docsDir, "project-context.md")),
+            latestMarkdownExists: fs.existsSync(path.join(resolvedProjectRoot, docsDir, "graph-insights", "latest.md")),
+            latestJsonExists: fs.existsSync(path.join(resolvedProjectRoot, docsDir, "graph-insights", "latest.json")),
+        };
+        const graphDocsMissing = !bootstrapState.latestMarkdownExists || !bootstrapState.latestJsonExists;
         const graphContext = await buildFeatureGraphContext({
             featureName,
             description,
+            projectRoot: projectRoot || undefined,
             signal: context?.signal,
         });
         const graphStatusNote = graphContext.available
-            ? `图谱增强: 可用（${graphContext.mode}）`
-            : "图谱增强: 已降级（自动回退）";
+            ? `任务图谱收敛: 可用（${graphContext.mode}）`
+            : "任务图谱收敛: 已降级（自动回退）";
         const graphGuideSection = `
 
-## 🧠 代码图谱上下文（可选增强）
-- 状态: ${graphContext.available ? "可用" : "降级"}
-- 摘要: ${graphContext.summary}
+## 🧠 代码图谱上下文
+- 基线入口: ${graphDocs.latestMarkdownPath}
+- 基线结构化副本: ${graphDocs.latestJsonPath}
+- 基线状态: ${graphDocsMissing ? "缺失（需要补初始化）" : "可用"}
+- 任务级收敛: ${graphContext.available ? "可用" : "降级"}
+- 任务级摘要: ${graphContext.summary}
 ${graphContext.highlights.length > 0
-            ? `- 线索:\n${graphContext.highlights.slice(0, 3).map((item) => `  - ${item}`).join("\n")}`
-            : "- 线索: 无"}
+            ? `- 任务级线索:\n${graphContext.highlights.slice(0, 3).map((item) => `  - ${item}`).join("\n")}`
+            : "- 任务级线索: 无"}
+- 使用方式: 先参考基线图谱，再使用本次任务图谱线索约束模块边界和改动范围
 `;
         const estimateCodeContext = [
             `参考生成的 ${docsDir}/specs/${featureName}/tasks.md`,
+            `如存在 ${graphDocs.latestMarkdownPath}，请一并参考其中的模块依赖和调用链摘要`,
             ...(graphContext.available
                 ? [
-                    graphContext.summary ? `图谱摘要: ${graphContext.summary}` : "",
-                    ...graphContext.highlights.slice(0, 2).map((item) => `图谱线索: ${item}`),
+                    graphContext.summary ? `任务图谱摘要: ${graphContext.summary}` : "",
+                    ...graphContext.highlights.slice(0, 2).map((item) => `任务图谱线索: ${item}`),
                 ]
                 : []),
         ]
@@ -281,6 +306,17 @@ ${graphContext.highlights.length > 0
             const plan = {
                 mode: 'delegated',
                 steps: [
+                    {
+                        id: 'context',
+                        tool: 'init_project_context',
+                        when: `缺少 ${docsDir}/project-context.md 或 ${graphDocs.latestMarkdownPath} / ${graphDocs.latestJsonPath}`,
+                        args: {
+                            docs_dir: docsDir,
+                            ...(projectRoot ? { project_root: projectRoot } : {}),
+                        },
+                        outputs: [`${docsDir}/project-context.md`, graphDocs.latestMarkdownPath, graphDocs.latestJsonPath],
+                        note: `兼容老项目：即使已有旧版 project-context，只要缺少图谱文档，也要先补齐 ${graphDocs.latestMarkdownPath}`,
+                    },
                     {
                         id: 'loop-1',
                         tool: 'ask_user',
@@ -333,6 +369,7 @@ ${graphContext.highlights.length > 0
             const guide = (header + LOOP_PROMPT_TEMPLATE
                 .replace(/{feature_name}/g, featureName)
                 .replace(/{description}/g, description)
+                .replace(/{project_root}/g, (projectRoot || process.cwd()).replace(/\\/g, "/"))
                 .replace(/{question_budget}/g, String(questionBudget))
                 .replace(/{assumption_cap}/g, String(assumptionCap)))
                 + graphGuideSection;
@@ -361,6 +398,11 @@ ${graphContext.highlights.length > 0
                 },
                 metadata: {
                     plan,
+                    graphDocs,
+                    bootstrapState: {
+                        ...bootstrapState,
+                        graphDocsMissing,
+                    },
                     graphContext,
                 },
             };
@@ -383,6 +425,7 @@ ${graphContext.highlights.length > 0
             .replace(/{feature_name}/g, featureName)
             .replace(/{description}/g, description)
             .replace(/{docs_dir}/g, docsDir)
+            .replace(/{project_root}/g, (projectRoot || process.cwd()).replace(/\\/g, "/"))
             .replace(/{template_profile}/g, templateProfile))
             + graphGuideSection;
         const plan = {
@@ -391,9 +434,13 @@ ${graphContext.highlights.length > 0
                 {
                     id: 'context',
                     tool: 'init_project_context',
-                    when: `缺少 ${docsDir}/project-context.md`,
-                    args: { docs_dir: docsDir },
-                    outputs: [`${docsDir}/project-context.md`],
+                    when: `缺少 ${docsDir}/project-context.md 或 ${graphDocs.latestMarkdownPath} / ${graphDocs.latestJsonPath}`,
+                    args: {
+                        docs_dir: docsDir,
+                        ...(projectRoot ? { project_root: projectRoot } : {}),
+                    },
+                    outputs: [`${docsDir}/project-context.md`, graphDocs.latestMarkdownPath, graphDocs.latestJsonPath],
+                    note: `兼容老项目：即使已有旧版 project-context，只要缺少图谱文档，也要先补齐 ${graphDocs.latestMarkdownPath}`,
                 },
                 {
                     id: 'spec',
@@ -424,7 +471,7 @@ ${graphContext.highlights.length > 0
                 {
                     name: '检查项目上下文',
                     status: 'pending',
-                    description: `检查 ${docsDir}/project-context.md 是否存在，如不存在则调用 init_project_context`,
+                    description: `检查 ${docsDir}/project-context.md 与 graph-insights/latest.* 是否存在，缺失则调用 init_project_context`,
                 },
                 {
                     name: '生成功能规格',
@@ -440,6 +487,8 @@ ${graphContext.highlights.length > 0
             artifacts: [],
             nextSteps: [
                 '检查并读取项目上下文文档',
+                `如果缺少 ${graphDocs.latestMarkdownPath} / ${graphDocs.latestJsonPath}，先调用 init_project_context 补齐图谱初始化`,
+                `优先读取 ${graphDocs.latestMarkdownPath} 获取模块依赖与调用链摘要`,
                 '调用 add_feature 工具生成功能规格文档',
                 '调用 estimate 工具进行工作量估算',
                 '按照 tasks.md 开始开发',
@@ -466,6 +515,11 @@ ${graphContext.highlights.length > 0
             dependencies: [],
             metadata: {
                 plan,
+                graphDocs,
+                bootstrapState: {
+                    ...bootstrapState,
+                    graphDocsMissing,
+                },
                 graphContext,
             },
         };

package/docs/data/tools.js

@@ -1,9 +1,9 @@
 // MCP Probe Kit 工具数据
 const toolsData = {
   workflow: [
-    {
-      name: 'start_feature',
-      description: '完整的功能开发工作流编排：检查上下文 → 生成规格 → 估算工作量',
+    {
+      name: 'start_feature',
+      description: '完整的功能开发工作流编排：补齐图谱基线 → 刷新 GitNexus 图谱 → 收敛需求范围 → 生成规格 → 估算工作量',
       schema: 'FeatureReportSchema',
       params: [
         { name: 'description', type: 'string', required: false, desc: '功能详细描述' },
@@ -15,28 +15,29 @@ const toolsData = {
         { name: 'loop_question_budget', type: 'number', required: false, desc: '每轮最多提问数量（默认 5）' },
         { name: 'loop_assumption_cap', type: 'number', required: false, desc: '每轮假设上限（默认 3）' }
       ],
-      usage: '用于启动完整的功能开发流程，自动生成需求文档、设计方案和工作量估算',
+      usage: '用于启动完整的功能开发流程，自动补齐 graph-insights，并通过 GitNexus 的 query/context/impact 收敛需求范围后生成规格与估算',
       example: `// 使用示例
 你: 请使用 start_feature 工具开发用户认证功能
 
 description: "添加用户认证功能，支持邮箱登录"
 feature_name: "user-auth"`
     },
-    {
-      name: 'start_bugfix',
-      description: 'Bug 修复工作流编排：检查上下文 → 分析定位 → 修复方案 → 生成测试',
-      schema: 'BugFixReportSchema',
-      params: [
-        { name: 'error_message', type: 'string', required: true, desc: '错误信息' },
-        { name: 'stack_trace', type: 'string', required: false, desc: '堆栈跟踪信息' },
-        { name: 'code_context', type: 'string', required: false, desc: '相关代码上下文' },
-        { name: 'template_profile', type: 'string', required: false, desc: '模板档位：auto、guided 或 strict' },
+    {
+      name: 'start_bugfix',
+      description: 'Bug 修复工作流编排：补齐图谱基线 → 刷新 GitNexus 图谱 → 收敛故障边界 → TBP 8 步真因分析 → 修复方案 → 生成测试',
+      schema: 'BugFixReportSchema',
+      params: [
+        { name: 'error_message', type: 'string', required: true, desc: '错误信息' },
+        { name: 'stack_trace', type: 'string', required: false, desc: '堆栈跟踪信息' },
+        { name: 'code_context', type: 'string', required: false, desc: '相关代码上下文' },
+        { name: 'analysis_mode', type: 'string', required: false, desc: '分析方法，默认 tbp8（先分析再修）' },
+        { name: 'template_profile', type: 'string', required: false, desc: '模板档位：auto、guided 或 strict' },
         { name: 'requirements_mode', type: 'string', required: false, desc: '需求模式：steady 或 loop' },
         { name: 'loop_max_rounds', type: 'number', required: false, desc: '需求 loop 最大轮次（默认 2）' },
         { name: 'loop_question_budget', type: 'number', required: false, desc: '每轮最多提问数量（默认 5）' },
         { name: 'loop_assumption_cap', type: 'number', required: false, desc: '每轮假设上限（默认 3）' }
       ],
-      usage: '用于系统化修复Bug，提供完整的分析、定位、修复和测试方案',
+      usage: '适用于找问题、修 bug、排查异常、定位回归；会先补齐 graph-insights 并用 GitNexus 收敛边界，再按 TBP 8 步法闭合真因后修复',
       example: `// 使用示例
 你: 请使用 start_bugfix 工具修复登录失败的问题
 
@@ -147,7 +148,7 @@ focus: "security"`
         { name: 'max_depth', type: 'number', required: false, desc: 'impact 最大深度，默认 3' },
         { name: 'include_tests', type: 'boolean', required: false, desc: 'impact 是否包含测试文件，默认 false' }
       ],
-      usage: '用于快速获取代码图谱线索，并为 start_feature/start_bugfix 提供可选增强',
+      usage: '用于刷新 GitNexus 图谱、获取任务级调用链/上下文/影响面，并把结果保存到 docs/graph-insights 与 project-context 索引',
       example: `// 使用示例
 你: 请使用 code_insight 工具分析登录相关调用链
 
@@ -156,14 +157,15 @@ query: "authentication middleware"`
     },
     {
       name: 'fix_bug',
-      description: 'Bug 修复指导，提供根因分析、修复计划、测试计划和预防措施',
-      schema: 'BugAnalysisSchema',
-      params: [
-        { name: 'error_message', type: 'string', required: true, desc: '错误信息' },
-        { name: 'stack_trace', type: 'string', required: false, desc: '堆栈跟踪' },
-        { name: 'code_context', type: 'string', required: false, desc: '相关代码' }
-      ],
-      usage: '提供完整的 Bug 修复指导，包含根因分析、修复方案、测试计划和预防措施',
+      description: '基于 TBP 8 步法的 Bug 真因分析与修复指导，输出证据链、修复计划、测试计划和预防措施',
+      schema: 'BugAnalysisSchema',
+      params: [
+        { name: 'error_message', type: 'string', required: true, desc: '错误信息' },
+        { name: 'stack_trace', type: 'string', required: false, desc: '堆栈跟踪' },
+        { name: 'code_context', type: 'string', required: false, desc: '相关代码' },
+        { name: 'analysis_mode', type: 'string', required: false, desc: '分析方法，默认 tbp8（先分析再修）' }
+      ],
+      usage: '适用于先找真因再修，帮助闭合现象、时间线、边界、真因和修复之间的因果链',
       example: `// 使用示例
 你: 请使用 fix_bug 工具修复这个问题
 
@@ -195,10 +197,10 @@ goal: "reduce_complexity"`
     }
   ],
   git: [
-    {
-      name: 'gencommit',
-      description: '根据代码变更自动生成符合 Conventional Commits 规范的 Git commit 消息',
-      schema: 'CommitMessageSchema',
+    {
+      name: 'gencommit',
+      description: '根据代码变更自动生成符合 Conventional Commits 规范的 Git commit 消息',
+      schema: 'CommitGuidanceSchema',
       params: [
         { name: 'changes', type: 'string', required: false, desc: '代码变更内容，可以是 git diff 输出、变更描述或自然语言' },
         { name: 'type', type: 'string', required: false, desc: 'Commit 类型：feat、fix、docs、style、chore、refactor、test，会自动识别' }
@@ -265,14 +267,14 @@ framework: "jest"`
 input: "创建一个任务管理系统，支持任务创建、分配、跟踪"
 project_name: "TaskManager"`
     },
-    {
-      name: 'init_project_context',
-      description: '生成项目上下文文档（技术栈/架构/编码规范）',
+    {
+      name: 'init_project_context',
+      description: '生成或维护项目上下文文档，并补齐 graph-insights 图谱基线入口',
       schema: 'ProjectContextSchema',
       params: [
         { name: 'docs_dir', type: 'string', required: false, desc: '文档目录，默认 docs' }
       ],
-      usage: '生成项目上下文文档，帮助团队快速上手',
+      usage: '新项目生成上下文骨架；老项目若已有 project-context.md，则保留旧文档，仅补 graph-insights 图谱文档与索引入口',
       example: `// 使用示例
 你: 请使用 init_project_context 工具生成项目上下文`
     },

package/docs/i18n/all-tools/en.json

@@ -71,12 +71,12 @@
   },
   "toolsData": {
     "start_feature": {
-      "description": "Complete feature development workflow orchestration: check context → generate specs → estimate workload",
-      "usage": "Used to initiate complete feature development process, automatically generating requirement documents, design plans, and workload estimates"
+      "description": "Complete feature development workflow orchestration: bootstrap graph baseline → refresh GitNexus index → narrow scope → generate specs → estimate workload",
+      "usage": "Used to start the full feature flow, backfill graph-insights when missing, then use GitNexus query/context/impact analysis to narrow scope before spec and estimation"
     },
     "start_bugfix": {
-      "description": "Bug fix workflow orchestration: check context → analyze and locate → fix solution → generate tests",
-      "usage": "Used for systematic bug fixing, providing complete analysis, location, fix, and test solutions"
+      "description": "Bug fix workflow orchestration: bootstrap graph baseline → refresh GitNexus index → narrow failure boundary → TBP 8-step root-cause analysis → fix plan → generate tests",
+      "usage": "Use it for bugs, regressions, and anomalies; it backfills graph-insights first and uses GitNexus to constrain boundary and impact before TBP RCA"
     },
     "start_onboard": {
       "description": "Project onboarding workflow: generate context documentation to help new members quickly understand the project",
@@ -99,8 +99,8 @@
       "usage": "Comprehensive code quality review, outputting structured issue list (severity/category/suggestion)"
     },
     "fix_bug": {
-      "description": "Bug fix guidance, providing root cause analysis, fix plan, test plan, and prevention measures",
-      "usage": "Provide complete bug fix guidance, including root cause analysis, fix solution, test plan, and prevention measures"
+      "description": "TBP 8-step bug RCA and repair guidance with evidence chain, fix plan, test plan, and prevention measures",
+      "usage": "Use it when you need to find the true cause first and close the chain from symptom and boundary to repair"
     },
     "refactor": {
       "description": "Refactoring suggestion tool, analyzing code structure, providing refactoring steps, risk assessment, and rollback plan",
@@ -123,8 +123,8 @@
       "usage": "Generate requirement/design/task documents following Spec-Driven Development approach"
     },
     "init_project_context": {
-      "description": "Generate project context documentation (tech stack/architecture/coding standards)",
-      "usage": "Generate project context documentation to help team quickly get started"
+      "description": "Generate or maintain project context documentation and bootstrap graph-insights entry points",
+      "usage": "Creates context docs for new projects; if project-context.md already exists, it preserves the old docs and only backfills graph-insights plus the index entry"
     },
     "add_feature": {
       "description": "Generate new feature specification documents (requirements/design/task list) based on project context",
@@ -156,7 +156,7 @@
     },
     "code_insight": {
       "description": "Code graph insight tool, bridging GitNexus to analyze call chains, context, and impact (auto-degrades when unavailable)",
-      "usage": "Quickly obtain graph insights and enhance start_feature/start_bugfix planning"
+      "usage": "Refresh the GitNexus index, perform task-level call-chain/context/impact analysis, and persist results to docs/graph-insights plus the project-context index"
     }
   }
 }

package/docs/i18n/all-tools/ja.json

@@ -71,12 +71,12 @@
   },
   "toolsData": {
     "start_feature": {
-      "description": "完全な機能開発ワークフローオーケストレーション：コンテキストチェック → 仕様生成 → 作業量見積もり",
-      "usage": "完全な機能開発プロセスを開始し、要件ドキュメント、設計計画、作業量見積もりを自動生成します"
+      "description": "完全な機能開発ワークフローオーケストレーション：グラフ基線補完 → GitNexus 更新 → 範囲収束 → 仕様生成 → 作業量見積もり",
+      "usage": "不足している graph-insights を補完し、GitNexus の query/context/impact で範囲を絞ったうえで仕様と見積もりを生成します"
     },
     "start_bugfix": {
-      "description": "バグ修正ワークフローオーケストレーション：コンテキストチェック → 分析と特定 → 修正ソリューション → テスト生成",
-      "usage": "体系的なバグ修正に使用され、完全な分析、特定、修正、テストソリューションを提供します"
+      "description": "バグ修正ワークフローオーケストレーション：グラフ基線補完 → GitNexus 更新 → 障害境界の収束 → TBP 8段階の真因分析 → 修正方針 → テスト生成",
+      "usage": "バグ・回帰・異常調査向け。先に graph-insights を補完し、GitNexus で境界と影響面を絞った後に TBP RCA を進めます"
     },
     "start_onboard": {
       "description": "プロジェクトオンボーディングワークフロー：コンテキストドキュメントを生成し、新メンバーがプロジェクトを迅速に理解できるようにします",
@@ -99,8 +99,8 @@
       "usage": "包括的なコード品質レビュー、構造化された問題リスト（severity/category/suggestion）を出力します"
     },
     "fix_bug": {
-      "description": "バグ修正ガイダンス、根本原因分析、修正計画、テスト計画、予防措置を提供します",
-      "usage": "根本原因分析、修正ソリューション、テスト計画、予防措置を含む完全なバグ修正ガイダンスを提供します"
+      "description": "TBP 8段階に基づくバグ真因分析と修正ガイダンス。証拠連鎖、修正計画、テスト計画、再発防止策を返します",
+      "usage": "真因を先に特定したいときに使います。現象・境界・真因・修正までの因果連鎖を閉じます"
     },
     "refactor": {
       "description": "リファクタリング提案ツール、コード構造を分析し、リファクタリング手順、リスク評価、ロールバック計画を提供します",
@@ -123,8 +123,8 @@
       "usage": "Spec-Driven Developmentアプローチに従って要件/設計/タスクドキュメントを生成します"
     },
     "init_project_context": {
-      "description": "プロジェクトコンテキストドキュメント（技術スタック/アーキテクチャ/コーディング標準）を生成します",
-      "usage": "チームが迅速に開始できるようにプロジェクトコンテキストドキュメントを生成します"
+      "description": "プロジェクトコンテキスト文書を生成・維持し、graph-insights の基線入口を補完します",
+      "usage": "新規プロジェクトでは骨組みを生成し、既存の project-context.md がある場合は上書きせず graph-insights と索引入口だけを補完します"
     },
     "add_feature": {
       "description": "プロジェクトコンテキストに基づいて新機能仕様ドキュメント（要件/設計/タスクリスト）を生成します",
@@ -156,7 +156,7 @@
     },
     "code_insight": {
       "description": "コードグラフ洞察ツール。GitNexus をブリッジして呼び出し連鎖、コンテキスト、影響範囲を分析（利用不可時は自動で劣化）",
-      "usage": "コードグラフの手がかりを素早く取得し、start_feature/start_bugfix の計画を強化します"
+      "usage": "GitNexus インデックスを更新し、タスク単位の呼び出し連鎖・コンテキスト・影響範囲を分析して docs/graph-insights と project-context 索引へ保存します"
     }
   }
 }

package/docs/i18n/all-tools/ko.json

@@ -71,12 +71,12 @@
   },
   "toolsData": {
     "start_feature": {
-      "description": "완전한 기능 개발 워크플로우 오케스트레이션: 컨텍스트 확인 → 사양 생성 → 작업량 추정",
-      "usage": "완전한 기능 개발 프로세스를 시작하여 요구사항 문서, 설계 계획 및 작업량 추정을 자동으로 생성합니다"
+      "description": "완전한 기능 개발 워크플로우 오케스트레이션: 그래프 베이스라인 보강 → GitNexus 갱신 → 범위 수렴 → 사양 생성 → 작업량 추정",
+      "usage": "누락된 graph-insights 를 먼저 보강하고 GitNexus query/context/impact 로 범위를 수렴시킨 뒤 사양과 추정을 생성합니다"
     },
     "start_bugfix": {
-      "description": "버그 수정 워크플로우 오케스트레이션: 컨텍스트 확인 → 분석 및 위치 파악 → 수정 솔루션 → 테스트 생성",
-      "usage": "체계적인 버그 수정에 사용되며 완전한 분석, 위치 파악, 수정 및 테스트 솔루션을 제공합니다"
+      "description": "버그 수정 워크플로우 오케스트레이션: 그래프 베이스라인 보강 → GitNexus 갱신 → 장애 경계 수렴 → TBP 8단계 근본원인 분석 → 수정 방안 → 테스트 생성",
+      "usage": "버그, 회귀, 이상 분석용. 먼저 graph-insights 를 보강하고 GitNexus 로 경계와 영향면을 좁힌 뒤 TBP RCA 를 진행합니다"
     },
     "start_onboard": {
       "description": "프로젝트 온보딩 워크플로우: 컨텍스트 문서를 생성하여 새 구성원이 프로젝트를 빠르게 이해할 수 있도록 돕습니다",
@@ -99,8 +99,8 @@
       "usage": "포괄적인 코드 품질 리뷰, 구조화된 문제 목록(severity/category/suggestion)을 출력합니다"
     },
     "fix_bug": {
-      "description": "버그 수정 가이드, 근본 원인 분석, 수정 계획, 테스트 계획 및 예방 조치를 제공합니다",
-      "usage": "근본 원인 분석, 수정 솔루션, 테스트 계획 및 예방 조치를 포함한 완전한 버그 수정 가이드를 제공합니다"
+      "description": "TBP 8단계 기반 버그 RCA 및 수정 가이드로 증거 사슬, 수정 계획, 테스트 계획, 예방 조치를 제공합니다",
+      "usage": "먼저 진짜 원인을 찾고 싶을 때 사용하며 현상, 경계, 진짜 원인, 수정까지의 인과 사슬을 닫아줍니다"
     },
     "refactor": {
       "description": "리팩토링 제안 도구, 코드 구조를 분석하고 리팩토링 단계, 위험 평가 및 롤백 계획을 제공합니다",
@@ -123,8 +123,8 @@
       "usage": "Spec-Driven Development 접근 방식에 따라 요구사항/설계/작업 문서를 생성합니다"
     },
     "init_project_context": {
-      "description": "프로젝트 컨텍스트 문서(기술 스택/아키텍처/코딩 표준)를 생성합니다",
-      "usage": "팀이 빠르게 시작할 수 있도록 프로젝트 컨텍스트 문서를 생성합니다"
+      "description": "프로젝트 컨텍스트 문서를 생성 또는 유지하고 graph-insights 베이스라인 진입점을 보강합니다",
+      "usage": "신규 프로젝트는 컨텍스트 골격을 생성하고, 기존 project-context.md 가 있으면 덮어쓰지 않고 graph-insights 와 인덱스 진입점만 보강합니다"
     },
     "add_feature": {
       "description": "프로젝트 컨텍스트를 기반으로 새 기능 사양 문서(요구사항/설계/작업 목록)를 생성합니다",
@@ -156,7 +156,7 @@
     },
     "code_insight": {
       "description": "코드 그래프 인사이트 도구로 GitNexus를 브리지하여 호출 체인, 컨텍스트, 영향 범위를 분석합니다(사용 불가 시 자동 강등)",
-      "usage": "코드 그래프 단서를 빠르게 확보하고 start_feature/start_bugfix 계획을 강화합니다"
+      "usage": "GitNexus 인덱스를 갱신하고 작업 단위 호출 체인/컨텍스트/영향 범위를 분석한 뒤 결과를 docs/graph-insights 와 project-context 인덱스에 저장합니다"
     }
   }
 }

package/docs/i18n/all-tools/zh-CN.json

@@ -71,12 +71,12 @@
   },
   "toolsData": {
     "start_feature": {
-      "description": "完整的功能开发工作流编排：检查上下文 → 生成规格 → 估算工作量",
-      "usage": "用于启动完整的功能开发流程，自动生成需求文档、设计方案和工作量估算"
+      "description": "完整的功能开发工作流编排：补齐图谱基线 → 刷新 GitNexus 图谱 → 收敛需求范围 → 生成规格 → 估算工作量",
+      "usage": "用于启动完整的功能开发流程，自动补齐 graph-insights，并通过 GitNexus 的 query/context/impact 收敛需求范围后生成规格与估算"
     },
     "start_bugfix": {
-      "description": "Bug 修复工作流编排：检查上下文 → 分析定位 → 修复方案 → 生成测试",
-      "usage": "用于系统化修复Bug，提供完整的分析、定位、修复和测试方案"
+      "description": "Bug 修复工作流编排：补齐图谱基线 → 刷新 GitNexus 图谱 → 收敛故障边界 → TBP 8 步真因分析 → 修复方案 → 生成测试",
+      "usage": "适用于找问题、修 bug、排查异常、定位回归；会先补齐 graph-insights 并用 GitNexus 收敛边界，再按 TBP 8 步法闭合真因后修复"
     },
     "start_onboard": {
       "description": "项目上手工作流：生成上下文文档，帮助新成员快速了解项目",
@@ -99,8 +99,8 @@
       "usage": "全面审查代码质量，输出结构化问题清单（severity/category/suggestion）"
     },
     "fix_bug": {
-      "description": "Bug 修复指导，提供根因分析、修复计划、测试计划和预防措施",
-      "usage": "提供完整的 Bug 修复指导，包含根因分析、修复方案、测试计划和预防措施"
+      "description": "基于 TBP 8 步法的 Bug 真因分析与修复指导，输出证据链、修复计划、测试计划和预防措施",
+      "usage": "适用于先找真因再修，帮助闭合现象、时间线、边界、真因和修复之间的因果链"
     },
     "refactor": {
       "description": "重构建议工具，分析代码结构，提供重构步骤、风险评估和回滚计划",
@@ -123,8 +123,8 @@
       "usage": "按 Spec-Driven Development 方式生成需求/设计/任务文档"
     },
     "init_project_context": {
-      "description": "生成项目上下文文档（技术栈/架构/编码规范）",
-      "usage": "生成项目上下文文档，帮助团队快速上手"
+      "description": "生成或维护项目上下文文档，并补齐 graph-insights 图谱基线入口",
+      "usage": "新项目生成上下文骨架；老项目若已有 project-context.md，则保留旧文档，仅补 graph-insights 图谱文档与索引入口"
     },
     "add_feature": {
       "description": "生成新功能规格文档（需求/设计/任务清单），基于项目上下文",
@@ -156,7 +156,7 @@
     },
     "code_insight": {
       "description": "代码图谱洞察工具，桥接 GitNexus 分析调用链、上下文和影响面（不可用时自动降级）",
-      "usage": "用于快速获取代码图谱线索，并为 start_feature/start_bugfix 提供可选增强"
+      "usage": "用于刷新 GitNexus 图谱、获取任务级调用链/上下文/影响面，并把结果保存到 docs/graph-insights 与 project-context 索引"
     }
   }
 }