Grok Bot 工程负责人分享信任 Agent 代码产出的倒金字塔方法与复用 Prompt
Grok Bot 工程负责人 Lauren Tan 提出用倒金字塔结构提升对 Agent 代码产出的信任：把最多精力放在代码库改进（架构、类型与不变量、清晰边界），其次是静态分析（lint 规则、测试、CI、TLA+ 等验证），再到注释、AGENTS.md、skills 等文字约定，最后才是最难规模化的人工审查。
how do you trust your agents' work more? copy this post/link and give it to your @bot or agent!
- codebase improvements: this is just good software engineering - better architecture, stronger types and invariants, clear boundaries. agents love to copy what exists and take the shortest path, so make the easy thing the right thing. categorically eliminate problems through code and you won't need to think about it again.
- static analysis: lint rules, tests, CI, verification (eg TLA+). very token efficient ways to catch issues ahead of time.
- prose: comments, rules, AGENTS.md, skills - anything that can't be enforced and requires agent judgment. use it minimally, but do use /create-verification-skill.
- human review: the hardest to scale. at the rate agents land code, it's pretty much impossible to thoroughly review every PR, so spend that effort on the highest leverage point, designing an environment where agents do the right thing by default.
this forms an inverse pyramid: you want most of your effort at the top, least at the bottom. codebase improvements are deterministic, making it more token efficient, and lets you sleep more soundly at night.
install https://github.com/cursor/plugins/tree/main/pstack and create a new Project:
1. look through my slack/chat messages and code review comments where i've given feedback on PRs, code, architecture
2. use /recall on my past transcripts to learn how i steer agents
3. /poteto-mode use /correct and /architect on past commits to find the most common pitfalls agents fall into, then propose a plan to rearchitect the code i own so it's more agent friendly. answer open questions with prototyping rather than defer to me, and back the plan with real data.
4. before you begin, use /sharpen + /in-your-own-words and confirm this prompt with me
来源：Lauren Tan · x.com