The bigger payoff comes when fixing and maintaining happens in the background and your teams can focus on building. That's when you start doing things that weren't even in range before. Anthropic is on step 3 and pushing toward 4. Personally, I just hit level 4. Curious where you are -- what step is your team on?
更大的回报出现在修复与维护都能在后台完成、而你的团队可以把注意力放在构建上的时候。那时你就会开始做一些此前甚至都不在能力范围内的事。Anthropic 目前在第 3 步，并正朝着第 4 步推进。就我个人而言，我刚达到第 4 级。很好奇你们现在处在哪——你的团队处于哪一步？
Once your teams are bought in, how do you track it? Usage is worth watching (e.g. a dashboard), but it measures activity, not return. A better question: would you have spent engineering effort on this anyway? If yes, how much and what would it have cost in manual eng-hours? That's your return.
当你的团队都已经 buy in（认同并接受）之后，你要如何追踪这件事？usage（使用量）值得关注——比如看 dashboard（仪表盘）——但它衡量的是 activity（活动量），不是 return（回报）。一个更好的问题是：这件事你原本是否也会投入 engineering（工程）精力去做？如果会，要投入多少，以及按手工方式需要花费多少 eng-hours（工程工时）？这就是你的回报。
In practice that means giving Claude ways to verify its own work end to end. It means enabling auto mode for permissions, defaulting on automated code review and security review, and using interfaces that let you manage multiple agents at once (Agent view in CLI, Desktop app, iOS and Android apps, Tag). To get to higher levels it means /loop, /batch, dynamic workflows, and worktree isolation for subagents. It's not about a single feature, but rather using the right features with the right guardrails that enable Claude to automate entire classes of work in a way that your team can trust the output.
在实践中，这意味着要给 Claude 提供能够端到端验证其自身工作的方式。这意味着为权限启用 auto mode，默认开启自动化 code review 和 security review，并使用那些能让你同时管理多个 agent（智能体）的界面（CLI 中的 Agent view、Desktop app、iOS 和 Android apps、Tag）。要达到更高等级，则意味着使用 /loop、/batch、dynamic workflows（动态工作流），以及为 subagents 提供 worktree isolation（工作树隔离）。关键不在于某个单一功能，而在于结合合适的 guardrails（护栏机制）使用正确的功能，让 Claude 能以你的团队可以信任其输出的方式，将整类工作自动化。