cruise-control

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Cruise Control Mode 🚗💨

巡航控制模式 🚗💨

Automatic transmission for StackShift - Shift through all 6 gears sequentially without manual intervention.

StackShift的自动执行模式——无需人工干预，依次完成全部6个Gear的切换。

When to Use This Skill

何时使用该功能

Use cruise control when:

You want to run the entire workflow automatically
Don't need to review each step before proceeding
Trust StackShift to make reasonable defaults
Want unattended execution (kick it off and come back later)
Prefer automatic over manual transmission

Trigger Phrases:

"Run StackShift in cruise control mode"
"Automatically shift through all gears"
"Run the full workflow automatically"
"StackShift autopilot"

在以下场景使用巡航控制：

希望自动运行完整工作流
不需要在每个步骤前进行审核
信任StackShift会做出合理的默认选择
需要无人值守执行（启动后即可稍后再查看结果）
偏好自动模式而非手动模式

触发短语：

"以巡航控制模式运行StackShift"
"自动完成所有Gear的切换"
"自动运行完整工作流"
"StackShift自动驾驶"

What This Does

功能说明

Runs all 6 gears sequentially:

Gear 1: Analyze → Gear 2: Reverse Engineer → Gear 3: Create Specs →
Gear 4: Gap Analysis → Gear 5: Complete Spec → Gear 6: Implement

Without stopping between gears!

依次运行全部6个Gear：

Gear 1: 分析 → Gear 2: 逆向工程 → Gear 3: 创建规格 →
Gear 4: 差距分析 → Gear 5: 完善规格 → Gear 6: 实现

Gear之间无需停顿！

Setup

设置步骤

Initial Configuration (One-Time)

初始配置（仅需一次）

At the start, you'll be asked:

Route Selection:

Choose your route:
A) Greenfield - Shift to new tech stack
B) Brownfield - Manage existing code

Implementation Framework:

Choose implementation framework:
A) GitHub Spec Kit - Feature specs in .specify/, /speckit.* commands
B) BMAD Auto-Pilot - Auto-generate BMAD artifacts from reverse-eng docs
C) BMAD Method - Same docs, hands off to BMAD's collaborative agents
D) Architecture Only - Generate architecture.md with your constraints

Clarifications Handling: (Spec Kit only)

How to handle [NEEDS CLARIFICATION] markers?
A) Defer - Mark them, implement around them, clarify later
B) Prompt - Stop and ask questions interactively
C) Skip - Only implement fully-specified features

Implementation Scope: (Spec Kit only)

What to implement in Gear 6?
A) P0 only - Critical features only
B) P0 + P1 - Critical and high-value
C) All - Everything (may take hours/days)
D) None - Stop after specs are ready

BMAD Synthesize Mode: (BMAD Auto-Pilot only)

How should BMAD artifacts be generated?
A) YOLO - Fully automatic, no questions (~10 min)
B) Guided - Auto-fill + targeted questions (~15-20 min)

Note: Interactive mode is not available in cruise control (requires manual interaction).

Architecture Constraints: (Architecture Only, asked once)

Quick architecture setup:
- Tech stack: [Same as current / specify]
- Cloud provider: [AWS / GCP / Azure / Self-hosted]
- Scale: [Startup / Growing / Enterprise]
- Hard constraints: [free text or skip]

Then cruise control takes over!

Note: For BMAD Method, questions 3-6 are skipped. For BMAD Auto-Pilot, questions 3-4 are skipped. For Architecture Only, questions 3-5 are skipped.

启动时，系统会询问以下问题：

路径选择：

选择你的路径：
A) Greenfield - 迁移至新技术栈
B) Brownfield - 管理现有代码

实现框架：

选择实现框架：
A) GitHub Spec Kit - 功能规格存储在.specify/目录，使用/speckit.*命令
B) BMAD Auto-Pilot - 从逆向工程文档自动生成BMAD工件
C) BMAD Method - 使用相同文档，交由BMAD的协作Agent处理
D) Architecture Only - 根据你的约束条件生成architecture.md

澄清事项处理：（仅适用于Spec Kit）

如何处理[NEEDS CLARIFICATION]标记？
A) 延后 - 标记该事项，先绕开实现，之后再澄清
B) 提示 - 暂停并交互式询问问题
C) 跳过 - 仅实现完全明确的功能

实现范围：（仅适用于Spec Kit）

Gear 6中需要实现哪些内容？
A) 仅P0 - 仅实现关键功能
B) P0 + P1 - 实现关键及高价值功能
C) 全部 - 实现所有功能（可能需要数小时/数天）
D) 无 - 完成规格后即停止

BMAD合成模式：（仅适用于BMAD Auto-Pilot）

如何生成BMAD工件？
A) YOLO - 完全自动，无需提问（约10分钟）
B) 引导式 - 自动填充+定向提问（约15-20分钟）

注意：巡航控制模式下不支持交互式模式（需要人工交互）。

架构约束：（仅适用于Architecture Only，仅询问一次）

快速架构设置：
- 技术栈：[与当前相同 / 指定]
- 云服务商：[AWS / GCP / Azure / 自托管]
- 规模：[初创公司 / 成长中 / 企业级]
- 硬性约束：[自由文本或跳过]

之后巡航控制将接管全部流程！

注意：对于BMAD Method，将跳过问题3-6；对于BMAD Auto-Pilot，将跳过问题3-4；对于Architecture Only，将跳过问题3-5。

Execution Flow

执行流程

GitHub Spec Kit Path

GitHub Spec Kit路径

Gear 1: Analyze (Auto)

Gear 1: 分析（自动）

Detects tech stack
Assesses completeness
Sets route and framework (from your selections)
Saves state with
```
auto_mode: true
```
Run AST analysis for deep code inspection (
```
node scripts/run-ast-analysis.mjs analyze .
```
)
Cache results in
```
.stackshift-analysis/
```
for all subsequent gears
Auto-shifts to Gear 2 ✅

检测技术栈
评估完整性
设置路径和框架（基于你的选择）
保存状态并标记
```
auto_mode: true
```
运行AST分析以进行深度代码检查（
```
node scripts/run-ast-analysis.mjs analyze .
```
）
将结果缓存至
```
.stackshift-analysis/
```
目录，供后续所有Gear使用
自动切换至Gear 2 ✅

Gear 2: Reverse Engineer (Auto)

Gear 2: 逆向工程（自动）

Launches
```
stackshift:code-analyzer
```
agent
Extracts documentation based on route
Generates all 9 files (including integration-points.md)
Auto-shifts to Gear 3 ✅

启动
```
stackshift:code-analyzer
```
agent
根据路径提取文档
生成全部9个文件（包括integration-points.md）
自动切换至Gear 3 ✅

Gear 3: Create Specifications (Auto)

Gear 3: 创建规格（自动）

Calls automated spec generation (F002)
Generates constitution (appropriate template for route)
Creates all feature specs programmatically
Creates implementation plans for incomplete features
Sets up
```
/speckit.*
```
slash commands
Auto-shifts to Gear 4 ✅

调用自动规格生成功能（F002）
生成章程（根据路径选择合适的模板）
以编程方式创建所有功能规格
为不完整的功能创建实现计划
设置
```
/speckit.*
```
斜杠命令
自动切换至Gear 4 ✅

Gear 4: Gap Analysis (Auto)

Gear 4: 差距分析（自动）

Runs
```
/speckit.analyze
```
Identifies PARTIAL/MISSING features
Creates prioritized roadmap
Marks [NEEDS CLARIFICATION] items
Auto-shifts to Gear 5 ✅

运行
```
/speckit.analyze
```
识别PARTIAL/MISSING（部分缺失/完全缺失）的功能
创建优先级路线图
标记[NEEDS CLARIFICATION]事项
自动切换至Gear 5 ✅

Gear 5: Complete Specification (Conditional)

Gear 5: 完善规格（条件性）

If clarifications handling = "Defer": Skips, moves to Gear 6
If clarifications handling = "Prompt": Asks questions interactively, then continues
If clarifications handling = "Skip": Marks unclear features as P2, moves on
Auto-shifts to Gear 6 ✅

若澄清事项处理方式为“延后”：跳过该步骤，直接进入Gear 6
若澄清事项处理方式为“提示”：交互式询问问题，之后继续
若澄清事项处理方式为“跳过”：将不明确的功能标记为P2，继续流程
自动切换至Gear 6 ✅

Gear 6: Implement (Based on Scope)

Gear 6: 实现（基于范围）

If scope = "None": Stops, specs ready
If scope = "P0 only": Implements critical features only
If scope = "P0 + P1": Implements critical + high-value
If scope = "All": Implements everything
Uses
```
/speckit.tasks
```
and
```
/speckit.implement
```
for each feature
Completes! 🏁

若范围为“无”：停止，规格已就绪
若范围为“仅P0”：仅实现关键功能
若范围为“P0 + P1”：实现关键及高价值功能
若范围为“全部”：实现所有功能
对每个功能使用
```
/speckit.tasks
```
和
```
/speckit.implement
```
命令
完成！ 🏁

BMAD Auto-Pilot Path

BMAD Auto-Pilot路径

Gear 1: Analyze (Auto)

Gear 1: 分析（自动）

Detects tech stack
Assesses completeness
Sets route and framework (
```
bmad-autopilot
```
)
Saves state with
```
auto_mode: true
```
Auto-shifts to Gear 2 ✅

检测技术栈
评估完整性
设置路径和框架（
```
bmad-autopilot
```
）
保存状态并标记
```
auto_mode: true
```
自动切换至Gear 2 ✅

Gear 2: Reverse Engineer (Auto)

Gear 2: 逆向工程（自动）

Launches
```
stackshift:code-analyzer
```
agent
Extracts all 11 documentation files (including business-context.md and decision-rationale.md)
Generates all docs in
```
docs/reverse-engineering/
```
Auto-shifts to BMAD Synthesize ✅

启动
```
stackshift:code-analyzer
```
agent
提取全部11个文档文件（包括business-context.md和decision-rationale.md）
在
```
docs/reverse-engineering/
```
目录生成所有文档
自动切换至BMAD合成环节 ✅

Gears 3-5: Replaced by BMAD Synthesize

Gear 3-5: 替换为BMAD合成

Runs
```
/stackshift.bmad-synthesize
```
in selected mode (YOLO or Guided)
Auto-generates: prd.md, architecture.md, epics.md, ux-design-specification.md
Writes to
```
_bmad-output/planning-artifacts/
```
Auto-shifts to Gear 6 ✅

以选定模式（YOLO或引导式）运行
```
/stackshift.bmad-synthesize
```
自动生成：prd.md、architecture.md、epics.md、ux-design-specification.md
写入至
```
_bmad-output/planning-artifacts/
```
目录
自动切换至Gear 6 ✅

Gear 6: BMAD Handoff (Optional)

Gear 6: BMAD交接（可选）

If user wants BMAD refinement: Displays BMAD installation +
```
*workflow-init
```
instructions
If artifacts are sufficient: Marks workflow complete
StackShift completes! 🏁

若用户希望优化BMAD：显示BMAD安装及
```
*workflow-init
```
指令
若工件已足够：标记工作流完成
StackShift流程完成！ 🏁

BMAD Method Path (Full Collaborative)

BMAD Method路径（全协作式）

Gear 1: Analyze (Auto)

Gear 1: 分析（自动）

Detects tech stack
Assesses completeness
Sets route and framework (from your selections)
Saves state with
```
auto_mode: true
```
Auto-shifts to Gear 2 ✅

检测技术栈
评估完整性
设置路径和框架（基于你的选择）
保存状态并标记
```
auto_mode: true
```
自动切换至Gear 2 ✅

Gear 2: Reverse Engineer (Auto)

Gear 2: 逆向工程（自动）

Launches
```
stackshift:code-analyzer
```
agent
Extracts all 11 documentation files
Generates all docs in
```
docs/reverse-engineering/
```
Skips to Gear 6 ✅

启动
```
stackshift:code-analyzer
```
agent
提取全部11个文档文件
在
```
docs/reverse-engineering/
```
目录生成所有文档
直接跳至Gear 6 ✅

Gears 3-5: Skipped

Gear 3-5: 跳过

BMAD agents handle PRD creation, architecture, and clarifications collaboratively
StackShift's reverse-engineering docs provide rich context for BMAD

BMAD agent将协作处理PRD创建、架构设计及澄清事项
StackShift的逆向工程文档为BMAD提供丰富的上下文信息

Gear 6: BMAD Handoff

Gear 6: BMAD交接

Displays instructions for BMAD installation and setup
Provides
```
*workflow-init
```
command to start BMAD workflow
Explains how to point BMAD to
```
docs/reverse-engineering/
```
StackShift completes - BMAD takes over! 🏁

显示BMAD安装和设置的指令
提供
```
*workflow-init
```
命令以启动BMAD工作流
说明如何将BMAD指向
```
docs/reverse-engineering/
```
目录
StackShift流程完成 - 交由BMAD接管！ 🏁

Architecture Only Path

Architecture Only路径

Gear 1: Analyze (Auto)

Gear 1: 分析（自动）

Detects tech stack
Assesses completeness
Sets route and framework (
```
architect-only
```
)
Collects architecture constraints (tech stack, cloud, scale)
Saves state with
```
auto_mode: true
```
Auto-shifts to Gear 2 ✅

检测技术栈
评估完整性
设置路径和框架（
```
architect-only
```
）
收集架构约束（技术栈、云服务商、规模）
保存状态并标记
```
auto_mode: true
```
自动切换至Gear 2 ✅

Gear 2: Reverse Engineer (Auto)

Gear 2: 逆向工程（自动）

Launches
```
stackshift:code-analyzer
```
agent
Extracts all 11 documentation files
Generates all docs in
```
docs/reverse-engineering/
```
Auto-shifts to Architecture Generator ✅

启动
```
stackshift:code-analyzer
```
agent
提取全部11个文档文件
在
```
docs/reverse-engineering/
```
目录生成所有文档
自动切换至架构生成环节 ✅

Gears 3-5: Replaced by Architecture Generator

Gear 3-5: 替换为架构生成

Runs
```
/stackshift.architect
```
with user constraints from Gear 1
Generates architecture.md with Mermaid diagrams, ADRs, infrastructure
StackShift completes! 🏁

使用Gear 1中收集的用户约束运行
```
/stackshift.architect
```
生成包含Mermaid图、ADR、基础设施的architecture.md
StackShift流程完成！ 🏁

Progress Monitoring

进度监控

While cruise control is running, you can check progress:

bash

undefined

巡航控制运行时，你可以检查进度：

bash

undefined

Check current gear and progress

检查当前Gear及进度

cat .stackshift-state.json | jq '{currentStep, completedSteps, auto_mode}'

Watch progress in real-time

实时监控进度

watch -n 5 'cat .stackshift-state.json | jq .currentStep'

---

watch -n 5 'cat .stackshift-state.json | jq .currentStep'

---

Interrupting Cruise Control

中断巡航控制

You can stop cruise control at any time:

"Stop cruise control"
"Pause StackShift"
"Switch to manual mode"

This will:

Save current state
Set
```
auto_mode: false
```
Allow you to proceed manually from current gear

You can resume cruise control later:

"Resume cruise control from current gear"

你可以随时停止巡航控制：

"停止巡航控制"
"暂停StackShift"
"切换至手动模式"

执行后将：

保存当前状态
设置
```
auto_mode: false
```
允许你从当前Gear手动继续流程

你可以稍后恢复巡航控制：

"从当前Gear恢复巡航控制"

Example: Full Automatic Run

示例：完整自动运行

User: "Run StackShift in cruise control mode"

StackShift:
Setting up cruise control...

Choose your route:
A) Greenfield - Shift to new tech stack
B) Brownfield - Manage existing code

User: "B - Brownfield"

StackShift:
How to handle clarifications?
A) Defer - Clarify later
B) Prompt - Ask me now
C) Skip - Only implement clear features

User: "A - Defer"

StackShift:
Implementation scope?
A) P0 only
B) P0 + P1
C) All features
D) None (stop after specs)

User: "B - P0 + P1"

StackShift:
✅ Cruise control engaged! Shifting through all gears automatically...

🔍 Gear 1: Analyzing... ✅ Complete (2 min)
🔄 Gear 2: Reverse engineering... ✅ Complete (8 min)
📋 Gear 3: Creating specifications... ✅ Complete (5 min)
🔍 Gear 4: Gap analysis... ✅ Complete (3 min)
✨ Gear 5: Completing specs (deferred clarifications)... ✅ Complete (1 min)
🚀 Gear 6: Implementing P0 + P1 features... 🔄 In Progress (est. 45 min)

   Feature 1/8: user-authentication... ✅
   Feature 2/8: fish-management... ✅
   Feature 3/8: photo-upload... 🔄 In progress...

[... continues automatically ...]

🏁 All gears complete! Application at 85% implementation.

Deferred clarifications (3) saved in: .specify/memory/clarifications.md
You can resolve these later with: /speckit.clarify

用户："以巡航控制模式运行StackShift"

StackShift:
正在设置巡航控制...

选择你的路径：
A) Greenfield - 迁移至新技术栈
B) Brownfield - 管理现有代码

用户："B - Brownfield"

StackShift:
如何处理澄清事项？
A) 延后 - 稍后澄清
B) 提示 - 现在询问我
C) 跳过 - 仅实现明确的功能

用户："A - 延后"

StackShift:
实现范围？
A) 仅P0
B) P0 + P1
C) 全部功能
D) 无（完成规格后停止）

用户："B - P0 + P1"

StackShift:
✅ 巡航控制已启动！将自动完成所有Gear的切换...

🔍 Gear 1: 分析中... ✅ 完成（2分钟）
🔄 Gear 2: 逆向工程中... ✅ 完成（8分钟）
📋 Gear 3: 创建规格中... ✅ 完成（5分钟）
🔍 Gear 4: 差距分析中... ✅ 完成（3分钟）
✨ Gear 5: 完善规格（延后澄清事项）... ✅ 完成（1分钟）
🚀 Gear 6: 实现P0 + P1功能中... 🔄 进行中（预计45分钟）

   功能1/8: 用户认证... ✅
   功能2/8: 鱼类管理... ✅
   功能3/8: 照片上传... 🔄 进行中...

[... 自动继续执行 ...]

🏁 所有Gear已完成！应用实现进度达85%。

延后的澄清事项（3项）已保存至：.specify/memory/clarifications.md
你可稍后使用`/speckit.clarify`命令解决这些事项

Configuration Options

配置选项

Cruise control can be configured via state:

json

{
  "auto_mode": true,
  "auto_config": {
    "route": "brownfield",
    "clarifications_strategy": "defer",
    "implementation_scope": "p0_p1",
    "pause_between_gears": false,
    "notify_on_completion": true
  }
}

可通过状态文件配置巡航控制：

json

{
  "auto_mode": true,
  "auto_config": {
    "route": "brownfield",
    "clarifications_strategy": "defer",
    "implementation_scope": "p0_p1",
    "pause_between_gears": false,
    "notify_on_completion": true
  }
}

Use Cases

使用场景

1. Overnight Execution

1. 夜间执行

5pm: "Run cruise control, brownfield, P0+P1, defer clarifications"
9am: Check results, review generated specs, answer deferred questions

下午5点："运行巡航控制，Brownfield路径，P0+P1范围，延后澄清事项"
上午9点：查看结果，审阅生成的规格，回答延后的问题

2. Demo Mode

2. 演示模式

"Show me what StackShift does - run full demo"
→ Runs cruise control with sample project

"展示StackShift的功能——运行完整演示"
→ 使用示例项目运行巡航控制

Safety Features

安全特性

Checkpoints

检查点

Cruise control creates checkpoints at each gear:

State saved after each gear completes
Can resume from any checkpoint if interrupted
Rollback possible if issues detected

巡航控制会在每个Gear完成时创建检查点：

每个Gear完成后保存状态
中断后可从任意检查点恢复
若检测到问题，可回滚

Validation

验证

Before proceeding:

Validates output files were created
Checks for errors in previous gear
Ensures prerequisites met

在继续流程前：

验证输出文件已创建
检查前一个Gear是否存在错误
确保满足前置条件

User Intervention

用户干预

Pauses automatically if:

Critical error detected
```
/speckit.analyze
```
shows major inconsistencies
Implementation fails tests
Disk space low
Git conflicts detected

在以下情况时会自动暂停：

检测到严重错误
```
/speckit.analyze
```
显示重大不一致
实现过程中测试失败
磁盘空间不足
检测到Git冲突

Manual Override

手动覆盖

At any point, you can:

"Pause after current gear"
"Stop cruise control"
"Switch to manual mode"
"Take control"

State saved, you can continue manually from that point.

你可在任意时刻执行以下操作：

"当前Gear完成后暂停"
"停止巡航控制"
"切换至手动模式"
"接管控制"

状态将被保存，你可从该点手动继续流程。

Success Criteria

成功标准

GitHub Spec Kit Path

GitHub Spec Kit路径

After cruise control completes:

✅ All 6 gears complete
✅
```
.stackshift-state.json
```
shows 6/6 gears
✅ All output files generated
✅ GitHub Spec Kit initialized (
```
.specify/
```
directory)
✅ Features implemented (based on scope)
✅ Ready for production (or clarifications if deferred)

巡航控制完成后：

✅ 全部6个Gear已完成
✅
```
.stackshift-state.json
```
显示6/6个Gear已完成
✅ 所有输出文件已生成
✅ GitHub Spec Kit已初始化（
```
.specify/
```
目录）
✅ 已实现功能（基于范围）
✅ 可投入生产（或需解决延后的澄清事项）

BMAD Auto-Pilot Path

BMAD Auto-Pilot路径

After cruise control completes:

✅ Gears 1, 2 complete + BMAD Synthesize complete
✅
```
.stackshift-state.json
```
shows framework: "bmad-autopilot"
✅
```
docs/reverse-engineering/
```
with all 11 files generated
✅
```
_bmad-output/planning-artifacts/
```
with prd.md, architecture.md, epics.md, ux-design-specification.md
✅ Synthesis report with coverage percentages
✅ Ready for BMAD refinement or direct use

巡航控制完成后：

✅ Gear 1、2及BMAD合成环节已完成
✅
```
.stackshift-state.json
```
显示框架为"bmad-autopilot"
✅
```
docs/reverse-engineering/
```
目录已生成全部11个文件
✅
```
_bmad-output/planning-artifacts/
```
目录已生成prd.md、architecture.md、epics.md、ux-design-specification.md
✅ 生成包含覆盖率百分比的合成报告
✅ 可进行BMAD优化或直接使用

BMAD Method Path

BMAD Method路径

After cruise control completes:

✅ Gears 1, 2, 6 complete (3-5 skipped)
✅
```
.stackshift-state.json
```
shows framework: "bmad"
✅
```
docs/reverse-engineering/
```
with all 11 files generated
✅ BMAD handoff instructions displayed
✅ Ready for
```
*workflow-init
```
to create PRD/Architecture collaboratively

巡航控制完成后：

✅ Gear 1、2、6已完成（3-5已跳过）
✅
```
.stackshift-state.json
```
显示框架为"bmad"
✅
```
docs/reverse-engineering/
```
目录已生成全部11个文件
✅ 显示BMAD交接指令
✅ 可使用
```
*workflow-init
```
命令启动BMAD协作工作流

Architecture Only Path

Architecture Only路径

After cruise control completes:

✅ Gears 1, 2 complete + Architecture Generator complete
✅
```
.stackshift-state.json
```
shows framework: "architect-only"
✅
```
docs/reverse-engineering/
```
with all 11 files generated
✅
```
architecture.md
```
with Mermaid diagrams, ADRs, infrastructure recommendations
✅ Cost estimation and migration path included

巡航控制完成后：

✅ Gear 1、2及架构生成环节已完成
✅
```
.stackshift-state.json
```
显示框架为"architect-only"
✅
```
docs/reverse-engineering/
```
目录已生成全部11个文件
✅ 已生成包含Mermaid图、ADR、基础设施建议的architecture.md
✅ 包含成本估算及迁移路径

Technical Notes

技术说明

Cruise control is a special skill that orchestrates other skills
Each gear is still executed by its corresponding skill
Auto mode can be toggled on/off at any time
State tracks auto_mode for resume capability
Great for CI/CD, batch processing, or overnight runs

Remember: Cruise control is like automatic transmission - convenient and hands-off. Manual mode (using individual skills) gives you more control. Choose based on your needs!

🚗 Manual = Control each gear yourself 🤖 Cruise Control = Let StackShift handle it

Both get you to the same destination!

巡航控制是一种特殊功能，用于编排其他功能
每个Gear仍由其对应的功能执行
可随时开启/关闭自动模式
状态会跟踪auto_mode以支持恢复功能
非常适合CI/CD、批量处理或夜间运行

记住： 巡航控制就像自动变速箱——便捷且无需手动操作；手动模式（使用单个功能）则能提供更多控制权。可根据你的需求进行选择！

🚗 手动模式 = 自行控制每个Gear 🤖 巡航控制 = 让StackShift处理全部流程

两种模式都能带你抵达相同的目的地！