Lately I have been spending a lot of time on vibe coding.最近一段时间，我一直在折腾 vibe coding。
At first it was exciting. The agent writes code faster and faster. I can even send it a message from my phone and tell it to keep building. But a problem came with it: more and more code, and more and more docs.一开始很兴奋。Agent 写代码越来越快，我甚至可以在手机上给它发消息，让它继续开发。问题也随之出现：代码越来越多，文档也越来越多。
Soon I saw all kinds of files show up in the project:很快，我发现项目里开始出现各种文件：
README.md
PLAN.md
STATUS.md
PROGRESS.md
DECISIONS.md
TODO.md
...It looks professional. But I felt more and more uncomfortable.看起来很专业，但我越来越不舒服。
So I asked myself, and I asked the AI:我问自己，也问 AI：
Do we really need all of these?这些东西真的都有必要吗？
AI is very easy to over-documentAI 特别容易过度文档化
Markdown is becoming the standard of the AI era..md 文档正在变成 AI 时代的事实标准。
Because Markdown is the easiest thing for an LLM to read, change, write, and review.因为 Markdown 最容易被 LLM 读取、修改、生成和审查。
But here is the problem.但问题来了。
AI turns almost every small thing into a new doc.AI 很容易把每个问题都变成一个新文档。
Need to record a decision today? Make a decisions.md.今天需要记录决策？新建一个 decisions.md。
Need to sync status tomorrow? Make a status.md.明天需要同步状态？新建一个 status.md。
Need a handoff the day after? Add a handoff.md.后天需要交接？再来一个 handoff.md。
In the end the project has more and more docs, and the real problem becomes:最后项目里文档越来越多，而真正的问题变成了：
Which one is the source of truth?哪个才是真相源（Source of Truth）？
AI still thinks like the time before AIAI 还在用前 AI 时代的思维
The funny thing is, while I was talking about this with the AI, I found that the AI itself often falls back into the old way of project management.有趣的是，在和 AI 讨论这个问题时，我发现 AI 自己也经常陷入旧时代的项目管理思维。
It will naturally bring up things like:它会自然地提出：
blockers
needs_decision
active_issue
milestone
sprintThese make total sense in a human team.这些在人类团队里完全合理。
Because one developer may have to wait for another developer.因为一个开发者可能要等另一个开发者。
One task may run for days, or even weeks.一个任务可能持续几天甚至几周。
But in the agent world, a lot of this has changed.但在 Agent 世界里，很多事情已经变了。
If you are only missing a page, a script, or a test, most of the time this is not a blocker.如果只是缺一个页面、一个脚本、一个测试，大多数时候这根本不是 blocker。
You make an issue, and the agent finishes it fast.创建一个 Issue，Agent 很快就能完成。
There is really only one kind of real blocker:真正的 blocker 往往只有一种：
A human has to make a decision.需要人类做决定。
Like pricing.比如定价。
Like product direction.比如产品方向。
Like whether to ship.比如是否上线。
Does Status really need to be that complex?Status 真的需要那么复杂吗？
Later I started to look at Status again.后来我开始重新审视 Status。
At first I wanted it to give data to a dashboard.我原本想让它给 Dashboard 提供数据。
But the more I thought about it, the stranger it felt.但是越想越觉得奇怪。
If in the end a project's status is only this:如果一个项目的状态最终只有：
Attention:
- need to confirm the payment linkAttention:
- 需要确认支付链接then are all those status fields pointless?那么大量的状态字段是不是都没有意义？
A lot of the info can actually be computed live.很多信息其实都可以动态计算。
A lot of the info is already in GitHub issues, PRs, or the codebase.很多信息其实已经存在于 GitHub Issue、PR 或代码库里。
What is left in the end is the simplest thing:最后留下来的，反而是最简单的东西：
Does this project need me right now?这个项目现在需不需要我。
My answer for now我目前的答案
For now I lean more and more toward this:目前我越来越倾向于：
README.md
for humans
PLAN.md
for the agent
GitHub Issues
run the tasks
PR
keep the proof
Attention
where a human steps inREADME.md
给人看
PLAN.md
给 Agent 看
GitHub Issues
执行任务
PR
保存证据
Attention
人类介入入口README can have a roadmap, but it should not become a task system.README 可以有路线图，但不要成为任务系统。
An issue is a unit of work, not a project-management ritual.Issue 是执行单元，而不是项目管理仪式。
Attention is the thing that really needs a human.Attention 是真正需要人类处理的事情。
Other than that, a lot of docs are worth doubting.除此之外，很多文档其实都值得怀疑。
Because the biggest problem with AI may not be that it can't write code.因为 AI 最大的问题，可能不是不会写代码。
It is that it likes writing docs too much.而是太喜欢写文档。
And what we really need may not be more docs.而我们真正需要的，也许不是更多文档。
It is fewer. Clearer. Harder to go out of date.而是更少、更清晰、更难过时。