upgrade-assessment

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Upgrade Assessment

升级评估

Evaluate platform upgrade readiness for Claude model transitions, Claude Code version bumps, and OrchestKit plugin updates. Produces a structured JSON assessment report with a 0-10 readiness score across 6 dimensions.
评估Claude模型切换、Claude Code版本升级及OrchestKit插件更新的平台升级就绪情况。生成包含6个维度、0-10分就绪评分的结构化JSON评估报告。

When to Use

适用场景

  • Before upgrading the Claude model (e.g., Sonnet 4 to Opus 4.6)
  • Before upgrading Claude Code to a new major/minor version
  • Before upgrading OrchestKit to a new major version
  • When evaluating whether a team environment is ready for a platform change
  • As part of release planning for model or platform migrations
  • 在升级Claude模型之前(例如从Sonnet 4升级到Opus 4.6)
  • 在升级Claude Code至新的主/次版本之前
  • 在升级OrchestKit至新的主版本之前
  • 评估团队环境是否已准备好进行平台变更时
  • 作为模型或平台迁移发布规划的一部分

Quick Start

快速开始

bash
/ork:upgrade-assessment           # Interactive assessment
/ork:upgrade-assessment --json    # Machine-readable output

bash
/ork:upgrade-assessment           # 交互式评估
/ork:upgrade-assessment --json    # 机器可读格式输出

6-Phase Workflow

6阶段工作流

Phase 0: Scope Definition

阶段0:范围定义

Tool:
AskUserQuestion
Determine the assessment scope before scanning. Ask the user:
What type of upgrade are you assessing?
  1. Full platform - Model + CC version + OrchestKit (comprehensive)
  2. Model only - Switching Claude model (e.g., Sonnet 4.5 to Opus 4.6)
  3. CC version only - Claude Code version bump (e.g., 2.1.32 to 2.1.33)
  4. OrchestKit only - Plugin version upgrade (e.g., 5.x to 6.x)
Record the scope and target versions. If the user does not specify target versions, research the latest available in Phase 2.

工具:
AskUserQuestion
在扫描前确定评估范围。询问用户:
你正在评估哪种类型的升级?
  1. 全平台 - 模型 + CC版本 + OrchestKit(全面评估)
  2. 仅模型 - 切换Claude模型(例如从Sonnet 4.5到Opus 4.6)
  3. 仅CC版本 - Claude Code版本升级(例如从2.1.32到2.1.33)
  4. 仅OrchestKit - 插件版本升级(例如从5.x到6.x)
记录范围和目标版本。如果用户未指定目标版本,将在阶段2中调研最新可用版本。

Phase 1: Detection

阶段1:检测

Tools:
Bash
,
Read
,
Grep
,
Glob
工具:
Bash
,
Read
,
Grep
,
Glob

Precondition Checks

前置条件检查

Before scanning, verify the environment is assessable:
bash
undefined
扫描前,验证环境是否可评估:
bash
undefined

Verify we're in an OrchestKit project

验证当前处于OrchestKit项目中

[ -f CLAUDE.md ] || { echo "ERROR: No CLAUDE.md found — not an OrchestKit project"; exit 1; } [ -d src/skills ] || { echo "ERROR: No src/skills/ directory"; exit 1; } [ -d src/agents ] || { echo "ERROR: No src/agents/ directory"; exit 1; } [ -f src/hooks/hooks.json ] || { echo "WARNING: No hooks.json — hook assessment will be skipped"; }

If any required directory is missing, abort with a clear error. If optional components (hooks) are missing, continue with reduced scope and note it in the report.
[ -f CLAUDE.md ] || { echo "ERROR: 未找到CLAUDE.md — 这不是OrchestKit项目"; exit 1; } [ -d src/skills ] || { echo "ERROR: 不存在src/skills/目录"; exit 1; } [ -d src/agents ] || { echo "ERROR: 不存在src/agents/目录"; exit 1; } [ -f src/hooks/hooks.json ] || { echo "WARNING: 不存在hooks.json — 将跳过钩子评估"; }

如果任何必需目录缺失,将终止评估并给出明确错误。如果可选组件(钩子)缺失,将缩小评估范围继续执行,并在报告中说明。

Environment Detection

环境检测

Detect the current environment state:
bash
undefined
检测当前环境状态:
bash
undefined

1. Current Claude model

1. 当前Claude模型

Check CLAUDE.md, settings, or environment for model references

在CLAUDE.md、设置或环境变量中检查模型引用

grep -r "claude-" CLAUDE.md .claude/ 2>/dev/null | head -20
grep -r "claude-" CLAUDE.md .claude/ 2>/dev/null | head -20

2. Claude Code version

2. Claude Code版本

claude --version 2>/dev/null || echo "CC version not detectable from CLI"
claude --version 2>/dev/null || echo "无法从CLI检测CC版本"

3. OrchestKit version

3. OrchestKit版本

Check CLAUDE.md or package.json for version field

在CLAUDE.md或package.json中检查版本字段

grep "Current.*:" CLAUDE.md | head -5
grep "Current.*:" CLAUDE.md | head -5

4. Hooks configuration

4. 钩子配置

cat src/hooks/hooks.json | python3 -c "import sys,json; d=json.load(sys.stdin); print(f'Hooks: {len(d.get("hooks",[]))} entries')" 2>/dev/null
cat src/hooks/hooks.json | python3 -c "import sys,json; d=json.load(sys.stdin); print(f'Hooks: {len(d.get("hooks",[]))} 条记录')" 2>/dev/null

5. Skill and agent counts

5. Skill和Agent数量

ls src/skills/ | wc -l ls src/agents/ | wc -l

**Output:** Environment snapshot including:
- Current model ID (e.g., `claude-sonnet-4-5`)
- Current CC version (e.g., `2.1.33`)
- Current OrchestKit version (e.g., `6.0.0`)
- Hook count and bundle count
- Skill count and agent count

---
ls src/skills/ | wc -l ls src/agents/ | wc -l

**输出:** 环境快照包含:
- 当前模型ID(例如 `claude-sonnet-4-5`)
- 当前CC版本(例如 `2.1.33`)
- 当前OrchestKit版本(例如 `6.0.0`)
- 钩子数量和包数量
- Skill数量和Agent数量

---

Phase 2: Research

阶段2:调研

Tools:
WebSearch
,
WebFetch
Research the target versions for new capabilities and breaking changes:
  1. Model changes:
    • Search for the target model's capabilities (context window, output limits, new features)
    • Search for breaking changes or deprecations from the previous model
    • Check for new tool support or changed behavior
  2. CC version changes:
    • Search for Claude Code changelog or release notes
    • Identify new hook types, skill format changes, or agent format changes
    • Check for deprecated configuration fields
  3. OrchestKit changes:
    • Read CHANGELOG.md for the target version
    • Identify new skills, removed skills, or renamed skills
    • Check for hook migration requirements
Research queries:
"Claude {target_model} capabilities release notes"
"Claude Code {target_version} changelog breaking changes"
"Claude {target_model} vs {current_model} differences"

工具:
WebSearch
,
WebFetch
调研目标版本的新功能和破坏性变更:
  1. 模型变更:
    • 搜索目标模型的功能(上下文窗口、输出限制、新特性)
    • 搜索与上一版本相比的破坏性变更或废弃内容
    • 检查是否支持新工具或行为变更
  2. CC版本变更:
    • 搜索Claude Code的更新日志或发布说明
    • 识别新的钩子类型、Skill格式变更或Agent格式变更
    • 检查已废弃的配置字段
  3. OrchestKit变更:
    • 阅读目标版本的CHANGELOG.md
    • 识别新增、移除或重命名的Skill
    • 检查钩子迁移要求
调研查询:
"Claude {target_model} capabilities release notes"
"Claude Code {target_version} changelog breaking changes"
"Claude {target_model} vs {current_model} differences"

Phase 3: Codebase Scan

阶段3:代码库扫描

Tools:
Grep
,
Glob
,
Read
Scan the codebase for patterns affected by the upgrade:
bash
undefined
工具:
Grep
,
Glob
,
Read
扫描代码库中受升级影响的模式:
bash
undefined

1. Model references (hardcoded model IDs)

1. 模型引用(硬编码的模型ID)

grep -r "claude-opus-4\b|claude-sonnet-4\b|claude-haiku-3\b" src/ --include=".md" --include=".ts" --include="*.json"
grep -r "claude-opus-4\b|claude-sonnet-4\b|claude-haiku-3\b" src/ --include=".md" --include=".ts" --include="*.json"

2. Deprecated API patterns

2. 已废弃的API模式

grep -r "max_tokens_to_sample|stop_sequences|model.claude-2" src/ --include=".ts" --include="*.py"
grep -r "max_tokens_to_sample|stop_sequences|model.claude-2" src/ --include=".ts" --include="*.py"

3. CC version-gated features

3. CC版本 gated 特性

grep -r "CC 2.1.|claude-code.2.1." src/ --include=".md"
grep -r "CC 2.1.|claude-code.2.1." src/ --include=".md"

4. Hook compatibility (check for removed or renamed hook types)

4. 钩子兼容性(检查已移除或重命名的钩子类型)

grep -r "PreToolUse|PostToolUse|PermissionRequest|Stop|Notification" src/hooks/ --include=".ts" --include=".json"
grep -r "PreToolUse|PostToolUse|PermissionRequest|Stop|Notification" src/hooks/ --include=".ts" --include=".json"

5. Context window assumptions

5. 上下文窗口假设

grep -r "200000|200_000|128000|128_000|context.window|max_context" src/ --include=".ts" --include=".md" --include=".py"
grep -r "200000|200_000|128000|128_000|context.window|max_context" src/ --include=".ts" --include=".md" --include=".py"

6. Output token assumptions

6. 输出token假设

grep -r "max_tokens.*4096|max_tokens.8192|max_output|output.limit" src/ --include=".ts" --include=".py"

**Classify findings:**
- **CRITICAL**: Hardcoded model IDs, removed API fields, breaking hook changes
- **WARNING**: Outdated context window assumptions, deprecated patterns
- **INFO**: Version references in documentation, optional feature flags

---
grep -r "max_tokens.*4096|max_tokens.8192|max_output|output.limit" src/ --include=".ts" --include=".py"

**分类发现:**
- **CRITICAL(严重)**:硬编码模型ID、已移除的API字段、破坏性钩子变更
- **WARNING(警告)**:过时的上下文窗口假设、已废弃的模式
- **INFO(信息)**:文档中的版本引用、可选特性标记

---

Phase 4: Scoring

阶段4:评分

Tools: Internal assessment logic
Rate readiness 0-10 across 6 dimensions using the scoring rubric from
platform-upgrade-knowledge
.
工具: 内部评估逻辑
使用
platform-upgrade-knowledge
中的评分标准,对6个维度的就绪度进行0-10分评级。

Scoring Rubric Summary

评分标准摘要

DimensionWeightWhat It Measures
Model Compatibility0.25Hardcoded model refs, capability assumptions, output limit assumptions
Hook Compatibility0.20Hook type changes, async pattern changes, lifecycle changes
Skill Coverage0.15Skill format changes, deprecated skills, new required skills
Agent Readiness0.15Agent format changes, model field validity, tool availability
Memory Architecture0.10Memory tier changes, storage format changes, migration needs
CI/CD Pipeline0.15Test compatibility, build system changes, deployment config
维度权重衡量内容
模型兼容性0.25硬编码模型引用、功能假设、输出限制假设
钩子兼容性0.20钩子类型变更、异步模式变更、生命周期变更
Skill覆盖度0.15Skill格式变更、已废弃Skill、新增必需Skill
Agent就绪度0.15Agent格式变更、模型字段有效性、工具可用性
内存架构0.10内存层级变更、存储格式变更、迁移需求
CI/CD流水线0.15测试兼容性、构建系统变更、部署配置

Score Interpretation

分数解读

RangeLabelMeaning
9-10ReadyUpgrade with confidence, minimal changes needed
7-8Low RiskMinor adjustments required, safe to proceed
5-6Moderate RiskSeveral changes needed, plan a migration sprint
3-4High RiskSignificant rework required, thorough testing needed
1-2Critical RiskMajor incompatibilities, consider phased migration
0BlockedCannot upgrade without fundamental changes
范围标签含义
9-10就绪可放心升级,仅需少量变更
7-8低风险需进行微小调整,可安全执行升级
5-6中等风险需进行多项变更,需规划迁移迭代
3-4高风险需进行大量重构,需全面测试
1-2严重风险存在重大不兼容,考虑分阶段迁移
0阻塞不进行根本性变更无法升级

Weighted Score Calculation

加权分数计算

overall_score = sum(dimension_score * weight for each dimension)
overall_score = sum(dimension_score * weight for each dimension)

Per-Dimension Scoring Thresholds

各维度评分阈值

Score each dimension 0-10 based on Phase 3 findings:
Model Compatibility (weight: 0.25)
  • 10: No hardcoded model IDs, no capability assumptions
  • 8: Documentation-only model references (non-functional)
  • 6: 1-3 hardcoded model IDs in functional code
  • 4: Output token limits or context window hardcoded
  • 2: Model-specific API patterns (e.g., prefilling for Claude, function calling format)
  • 0: Core logic depends on model-specific behavior
Hook Compatibility (weight: 0.20)
  • 10: All hooks use current event types and async patterns
  • 8: Minor deprecation warnings, no functional impact
  • 6: 1-3 hooks use deprecated event types
  • 4: Hook input/output schema changed
  • 2: Hook lifecycle order changed
  • 0: Hook system replaced or fundamentally restructured
Skill Coverage (weight: 0.15)
  • 10: All skills use current frontmatter format, no stale references
  • 8: Minor version references outdated in skill content
  • 6: 1-5 skills reference deprecated features or removed capabilities
  • 4: Skill frontmatter schema changed (new required fields)
  • 2: Skill loading mechanism changed
  • 0: Skill format incompatible
Agent Readiness (weight: 0.15)
  • 10: All agents use valid model aliases, tools, and frontmatter
  • 8: 1-2 agents reference removed tools or deprecated fields
  • 6: Agent model field values changed meaning
  • 4: Agent frontmatter schema requires migration
  • 2: Agent tool availability significantly changed
  • 0: Agent system incompatible
Memory Architecture (weight: 0.10)
  • 10: Memory tiers unchanged, storage format stable
  • 8: New optional memory tier available
  • 6: Memory storage format changed (migration available)
  • 4: Memory tier behavior changed (e.g., scope semantics)
  • 2: Memory migration required with data transformation
  • 0: Memory system replaced
CI/CD Pipeline (weight: 0.15)
  • 10: All tests pass, build system unchanged
  • 8: Minor test assertion updates needed
  • 6: Test framework or runner version update needed
  • 4: Build configuration changes required
  • 2: CI pipeline restructure needed
  • 0: Build system incompatible

根据阶段3的发现,对每个维度进行0-10分评分:
模型兼容性(权重:0.25)
  • 10分:无硬编码模型ID,无功能假设
  • 8分:仅文档中存在模型引用(无功能影响)
  • 6分:功能代码中有1-3处硬编码模型ID
  • 4分:硬编码了输出token限制或上下文窗口
  • 2分:存在模型特定的API模式(例如Claude的预填充、函数调用格式)
  • 0分:核心逻辑依赖模型特定行为
钩子兼容性(权重:0.20)
  • 10分:所有钩子使用当前事件类型和异步模式
  • 8分:存在微小废弃警告,无功能影响
  • 6分:1-3个钩子使用已废弃的事件类型
  • 4分:钩子输入/输出 schema 变更
  • 2分:钩子生命周期顺序变更
  • 0分:钩子系统被替换或重构
Skill覆盖度(权重:0.15)
  • 10分:所有Skill使用当前前置格式,无过时引用
  • 8分:Skill内容中的版本引用过时
  • 6分:1-5个Skill引用已废弃特性或已移除功能
  • 4分:Skill前置schema变更(新增必填字段)
  • 2分:Skill加载机制变更
  • 0分:Skill格式不兼容
Agent就绪度(权重:0.15)
  • 10分:所有Agent使用有效的模型别名、工具和前置格式
  • 8分:1-2个Agent引用已移除工具或已废弃字段
  • 6分:Agent模型字段值含义变更
  • 4分:Agent前置schema需迁移
  • 2分:Agent工具可用性大幅变更
  • 0分:Agent系统不兼容
内存架构(权重:0.10)
  • 10分:内存层级未变更,存储格式稳定
  • 8分:新增可选内存层级
  • 6分:内存存储格式变更(提供迁移方案)
  • 4分:内存层级行为变更(例如范围语义)
  • 2分:内存迁移需进行数据转换
  • 0分:内存系统被替换
CI/CD流水线(权重:0.15)
  • 10分:所有测试通过,构建系统未变更
  • 8分:需更新少量测试断言
  • 6分:需更新测试框架或运行器版本
  • 4分:需变更构建配置
  • 2分:需重构CI流水线
  • 0分:构建系统不兼容

Phase 5: Recommendations

阶段5:建议

Tools: Assessment analysis
Generate prioritized action items based on Phase 3 findings and Phase 4 scores.
工具: 评估分析
根据阶段3的发现和阶段4的分数,生成优先级排序的行动项。

Priority Assignment Algorithm

优先级分配算法

Map dimension scores to priority levels:
For each finding from Phase 3:
  dimension_score = Phase 4 score for the finding's dimension

  if dimension_score <= 2:  priority = "P0"  # Blocker
  if dimension_score <= 4:  priority = "P1"  # Critical
  if dimension_score <= 6:  priority = "P2"  # Important
  if dimension_score <= 8:  priority = "P3"  # Nice-to-Have
  if dimension_score > 8:   # No action needed
将维度分数映射到优先级级别:
对于阶段3中的每个发现:
  dimension_score = 该发现对应维度的阶段4分数

  如果 dimension_score <= 2:  priority = "P0"  # 阻塞项
  如果 dimension_score <= 4:  priority = "P1"  # 严重项
  如果 dimension_score <= 6:  priority = "P2"  # 重要项
  如果 dimension_score <= 8:  priority = "P3"  # 优化项
  如果 dimension_score > 8:   # 无需操作

Priority Levels

优先级级别

PriorityCriteriaTimeline
P0 - BlockerScore 0-2 in any dimension; will break on upgradeBefore upgrade
P1 - CriticalScore 3-4; degraded functionality post-upgradeSame sprint
P2 - ImportantScore 5-6; works but suboptimalNext sprint
P3 - Nice-to-HaveScore 7-8; minor improvements availableBacklog
优先级标准时间线
P0 - 阻塞项任意维度分数0-2;升级后会导致崩溃升级前必须完成
P1 - 严重项分数3-4;升级后功能退化同一迭代完成
P2 - 重要项分数5-6;可运行但性能不佳下一迭代完成
P3 - 优化项分数7-8;可进行微小改进纳入积压任务

Effort Estimation

工作量估算

effort = "low"     # Single file, < 5 lines changed
effort = "medium"  # 2-5 files, or schema migration
effort = "high"    # 6+ files, or architectural change
effort = "low"     # 单个文件,变更少于5行
effort = "medium"  # 2-5个文件,或schema迁移
effort = "high"    # 6个以上文件,或架构变更

Recommendation Format

建议格式

Each recommendation includes:
  1. What: Description of the change needed
  2. Why: Impact if not addressed
  3. How: Specific steps or code changes
  4. Effort: Low (< 1 hour), Medium (1-4 hours), High (4+ hours)
  5. Files: List of affected files

每条建议包含:
  1. 内容:所需变更的描述
  2. 原因:不处理的影响
  3. 方法:具体步骤或代码变更
  4. 工作量:低(<1小时)、中(1-4小时)、高(4+小时)
  5. 文件:受影响的文件列表

Output Format

输出格式

The assessment produces a structured JSON report:
json
{
  "assessment": {
    "id": "upgrade-assessment-{timestamp}",
    "scope": "full|model-only|cc-only|ork-only",
    "timestamp": "2026-02-06T12:00:00Z"
  },
  "environment": {
    "current": {
      "model": "claude-sonnet-4-5",
      "ccVersion": "2.1.32",
      "orkVersion": "6.0.0",
      "hooks": 121,
      "skills": 199,
      "agents": 36
    },
    "target": {
      "model": "claude-opus-4-6",
      "ccVersion": "2.1.33",
      "orkVersion": "6.1.0"
    }
  },
  "scores": {
    "overall": 7.4,
    "dimensions": {
      "modelCompatibility": { "score": 8, "weight": 0.25, "weighted": 2.0 },
      "hookCompatibility": { "score": 9, "weight": 0.20, "weighted": 1.8 },
      "skillCoverage": { "score": 7, "weight": 0.15, "weighted": 1.05 },
      "agentReadiness": { "score": 7, "weight": 0.15, "weighted": 1.05 },
      "memoryArchitecture": { "score": 6, "weight": 0.10, "weighted": 0.6 },
      "cicdPipeline": { "score": 6, "weight": 0.15, "weighted": 0.9 }
    }
  },
  "findings": [
    {
      "severity": "CRITICAL",
      "dimension": "modelCompatibility",
      "description": "Hardcoded model ID 'claude-sonnet-4' in 3 agent files",
      "files": ["src/agents/code-reviewer.md", "src/agents/architect.md"],
      "recommendation": "Update model field to 'claude-opus-4-6' or use 'sonnet' alias"
    },
    {
      "severity": "WARNING",
      "dimension": "skillCoverage",
      "description": "Context window references assume 200K tokens, Opus 4.6 supports 1M",
      "files": ["src/skills/context-engineering/SKILL.md"],
      "recommendation": "Update token budget calculations for 1M context window"
    }
  ],
  "recommendations": [
    {
      "priority": "P0",
      "action": "Update hardcoded model references",
      "effort": "low",
      "files": ["src/agents/*.md"],
      "steps": [
        "Grep for 'claude-sonnet-4' and 'claude-opus-4' in src/",
        "Replace with target model ID or use alias",
        "Run npm run test:agents to validate"
      ]
    },
    {
      "priority": "P2",
      "action": "Update context budget calculations",
      "effort": "medium",
      "files": ["src/skills/context-engineering/SKILL.md"],
      "steps": [
        "Update MAX_CONTEXT values for new model",
        "Adjust compression triggers if context window changed",
        "Update documentation examples"
      ]
    }
  ],
  "summary": {
    "readiness": "Low Risk",
    "overallScore": 7.4,
    "blockers": 0,
    "criticalItems": 1,
    "totalFindings": 5,
    "estimatedEffort": "4-6 hours"
  }
}

评估将生成结构化JSON报告:
json
{
  "assessment": {
    "id": "upgrade-assessment-{timestamp}",
    "scope": "full|model-only|cc-only|ork-only",
    "timestamp": "2026-02-06T12:00:00Z"
  },
  "environment": {
    "current": {
      "model": "claude-sonnet-4-5",
      "ccVersion": "2.1.32",
      "orkVersion": "6.0.0",
      "hooks": 121,
      "skills": 199,
      "agents": 36
    },
    "target": {
      "model": "claude-opus-4-6",
      "ccVersion": "2.1.33",
      "orkVersion": "6.1.0"
    }
  },
  "scores": {
    "overall": 7.4,
    "dimensions": {
      "modelCompatibility": { "score": 8, "weight": 0.25, "weighted": 2.0 },
      "hookCompatibility": { "score": 9, "weight": 0.20, "weighted": 1.8 },
      "skillCoverage": { "score": 7, "weight": 0.15, "weighted": 1.05 },
      "agentReadiness": { "score": 7, "weight": 0.15, "weighted": 1.05 },
      "memoryArchitecture": { "score": 6, "weight": 0.10, "weighted": 0.6 },
      "cicdPipeline": { "score": 6, "weight": 0.15, "weighted": 0.9 }
    }
  },
  "findings": [
    {
      "severity": "CRITICAL",
      "dimension": "modelCompatibility",
      "description": "3个Agent文件中存在硬编码模型ID 'claude-sonnet-4'",
      "files": ["src/agents/code-reviewer.md", "src/agents/architect.md"],
      "recommendation": "将model字段更新为 'claude-opus-4-6' 或使用 'sonnet' 别名"
    },
    {
      "severity": "WARNING",
      "dimension": "skillCoverage",
      "description": "上下文窗口引用假设为200K token,而Opus 4.6支持1M",
      "files": ["src/skills/context-engineering/SKILL.md"],
      "recommendation": "针对1M上下文窗口更新token预算计算"
    }
  ],
  "recommendations": [
    {
      "priority": "P0",
      "action": "更新硬编码模型引用",
      "effort": "low",
      "files": ["src/agents/*.md"],
      "steps": [
        "在src/中搜索 'claude-sonnet-4' 和 'claude-opus-4'",
        "替换为目标模型ID或使用别名",
        "运行npm run test:agents验证"
      ]
    },
    {
      "priority": "P2",
      "action": "更新上下文预算计算",
      "effort": "medium",
      "files": ["src/skills/context-engineering/SKILL.md"],
      "steps": [
        "为新模型更新MAX_CONTEXT值",
        "如果上下文窗口变更,调整压缩触发条件",
        "更新文档示例"
      ]
    }
  ],
  "summary": {
    "readiness": "低风险",
    "overallScore": 7.4,
    "blockers": 0,
    "criticalItems": 1,
    "totalFindings": 5,
    "estimatedEffort": "4-6小时"
  }
}

Execution Notes

执行说明

For Model-Only Upgrades

仅模型升级

Focus on Phases 1, 2, and 3. Key areas:
  • Agent
    model:
    fields
  • Context window / output token assumptions
  • Capability-dependent skill content (e.g., vision, audio)
重点关注阶段1、2和3。核心领域:
  • Agent的
    model:
    字段
  • 上下文窗口/输出token假设
  • 依赖功能的Skill内容(例如视觉、音频)

For CC Version Upgrades

仅CC版本升级

Focus on hook compatibility and skill format:
  • Hook type registry changes
  • Skill frontmatter field additions/removals
  • Permission rule format changes
  • New built-in tools or removed tools
重点关注钩子兼容性和Skill格式:
  • 钩子类型注册表变更
  • Skill前置字段的增删
  • 权限规则格式变更
  • 新增或移除的内置工具

For OrchestKit Upgrades

仅OrchestKit升级

Focus on plugin structure:
  • Manifest schema changes
  • Build system changes
  • Skill/agent rename or removal
  • Hook source reorganization

重点关注插件结构:
  • 清单schema变更
  • 构建系统变更
  • Skill/Agent的重命名或移除
  • 钩子源文件重组

Rules Quick Reference

规则速查

RuleImpactWhat It Covers
knowledge-evaluationHIGH6-dimension scoring rubric, severity classification
knowledge-compatibilityHIGHVersion compatibility matrix, breaking change detection
规则影响覆盖内容
knowledge-evaluation6维度评分标准、严重性分类
knowledge-compatibility版本兼容性矩阵、破坏性变更检测

Related Skills

相关Skill

  • platform-upgrade-knowledge
    - Scoring rubric details and compatibility matrix
  • doctor
    - Post-upgrade health validation
  • explore
    - Codebase exploration for impact analysis
  • verify
    - Verification of changes after migration
  • devops-deployment
    - CI/CD pipeline updates
  • platform-upgrade-knowledge
    - 详细的维度评分标准和兼容性矩阵
  • doctor
    - 升级后健康状态验证
  • explore
    - 影响分析的代码库探索
  • verify
    - 迁移后变更验证
  • devops-deployment
    - CI/CD流水线更新

References

参考资料

  • See
    platform-upgrade-knowledge/references/scoring-rubric.md
    for detailed dimension scoring
  • See
    platform-upgrade-knowledge/references/compatibility-matrix.md
    for version compatibility tracking
  • 详细维度评分请查看
    platform-upgrade-knowledge/references/scoring-rubric.md
  • 版本兼容性跟踪请查看
    platform-upgrade-knowledge/references/compatibility-matrix.md