Structured guidance for capacity planning (load, headroom, scaling): confirm triggers, propose the stages below, and adapt if the user wants a lighter pass.

为 容量规划（负载、预留空间、扩展）提供结构化指导：确认触发条件，提出以下阶段，并根据用户需求调整。

When to Offer This Workflow 何时提供此工作流

Trigger conditions:

• User mentions capacity, headroom, scaling plans, or closely related work
• They want a structured workflow rather than ad-hoc tips
• They are preparing a review, rollout, or stakeholder communication

触发条件：

• 用户提及 capacity、headroom、scaling plans 或密切相关的工作
• 他们想要结构化的工作流而不是临时建议
• 他们正在准备审查、发布或利益相关者沟通

Initial offer: Explain the four stages briefly and ask whether to follow this workflow or work freeform. If they decline, continue in their preferred style.

初始报价： 简要解释四个阶段，并询问是否遵循此工作流或自由形式工作。如果他们拒绝，以他们偏好的风格继续。

Workflow Stages 工作流阶段

Stage 1: Clarify context & goals

Anchor on growth assumptions and seasonality. Ask what success looks like, constraints, and what must not break. Capture unknowns early.

阶段 1：澄清上下文和目标

围绕 增长假设和季节性 展开。询问成功是什么样的，约束条件，以及什么不能被破坏。尽早发现未知因素。

Stage 2: Design or plan the approach

Translate goals into a concrete plan around headroom and bottlenecks. Compare alternatives and explicit trade-offs; avoid implicit assumptions.

阶段 2：设计或规划方法

将目标转化为围绕 预留空间和瓶颈 的具体计划。比较替代方案和明确的权衡；避免隐含假设。

Stage 3: Implement, validate, and harden

Execute with verification loops tied to cost vs performance trade-offs. Prefer small steps, measurable checks, and rollback points where risk is high.

阶段 3：实施、验证和加固

执行与 成本与性能权衡 相关的验证循环。优先考虑小步骤、可衡量的检查和高风险时的回滚点。

Stage 4: Operate, communicate, and iterate

Close the loop with load tests and forecasts: monitoring, documentation, stakeholder updates, and lessons learned for the next cycle.

阶段 4：运营、沟通和迭代

通过 负载测试和预测 闭合循环：监控、文档、利益相关者更新以及下一轮的经验教训。

Checklist Before Completion 完成前的检查清单

• Goals and constraints are explicit for capacity planning
• Risks and trade-offs are stated, not hand-waved
• Verification steps match the change's impact (tests, canary, peer review)
• Operational follow-through is covered (monitoring, docs, owners)

• 容量规划的目标和约束是明确的
• 风险和权衡已说明，而非一带而过
• 验证步骤与变更的影响相匹配（测试、金丝雀发布、同行评审）
• 运营后续行动已涵盖（监控、文档、负责人）

Tips for Effective Guidance 有效指导的技巧

• Be procedural: stage-by-stage, with clear exit criteria
• Ask for missing context (environment, scale, deadlines) before prescribing
• Prefer checklists and concrete examples over generic platitudes
• If the user declines the workflow, switch to freeform help without lecturing

• 按程序进行：分阶段进行，并设定明确的退出标准
• 在给出建议之前，询问缺失的上下文（环境、规模、截止日期）
• 优先使用检查清单和具体示例，而不是泛泛而谈的套话
• 如果用户拒绝该工作流，改为自由形式的帮助，不要说教

Handling Deviations 处理偏差

• If the user wants to skip a stage: confirm and continue with what they need.
• If context is missing: ask targeted questions before strong recommendations.
• Prefer concrete examples, trade-offs, and verification steps over generic advice.

• 如果用户想跳过某个阶段：确认并继续他们需要的部分。
• 如果上下文缺失：在给出强烈建议之前提出有针对性的问题。
• 优先考虑具体示例、权衡和验证步骤，而不是泛泛的建议。

Quality Bar 质量标准

• Each recommendation should be actionable (what to do next).
• Call out failure modes relevant to capacity (security, scale, UX, or ops).
• Keep tone direct and respectful of the user's time.

• 每个建议都应该是 可操作的（下一步要做什么）。
• 指出与容量相关的 失败模式（安全、规模、用户体验或运营）。
• 保持语气直接，尊重用户的时间。