So, traditionally, in our planning stage, we would sit down, gather requirements, create PRDs, have workshops, talk to stakeholders, pulling it all together. In this new world, we start by getting the agents to interview us about the feature, the bug, or the product that we're building in order to build up context.
传统上，规划阶段我们会坐下来收集需求、写 PRD、开工作坊、和利益相关者谈话，再把材料拼在一起。而在这个新世界里，我们先让 agent 就我们正在做的功能、缺陷或产品来采访我们，以便积累上下文。
I use my own discovery skill called switch dimension discovery, you could use Realm me from Matt Pocock, or you could use something like requirements discovery from Cursor. So, what you want to do is make sure the agent asks you repeated questions until it has a complete understanding of the feature you're building or the bug you're trying to solve. You're dumping as much of your experience, domain experience, and context into this conversation.
我用的是自己的 discovery skill，叫 Switch Dimension discovery；你也可以用 Matt Pocock 的 Realm me，或 Cursor 里类似 requirements discovery 的东西。关键是让 agent 反复提问，直到它完整理解你要做的功能或要修的缺陷。你要把自己的经验、领域经验和上下文尽量倒进这次对话里。
So, the agent synthesizes pain points straight from the sources, and then captures them in this intent.md file, which is human-readable and machine-actionable. So, Anthropic is formalizing this idea around an intent.md file. So, in the traditional SDLC, the idea passed to a backlog of user entries, user stories, story points, ownership transfers, handoff.
于是 agent 直接从这些来源里综合痛点，再把它们写进 intent.md 文件；这份文件既是人能读的，也是机器可执行的。所以 Anthropic 正在把 intent.md 这个想法正式化。在传统 SDLC 里，想法会进入 backlog、用户故事、story points，所有权会转移、会交接。
What we're talking about in the AI-native world is the originator of the issue, the feature, the product, whatever, brainstorms with Claude and writes the result down as the intent.md. So, for each one of these steps as we move through, we're going to be developing what's called an artifact chain. First, we start with an intent.md file, then we're going to have a spec, etc., as we go through the steps. That's building the artifact chain.
而在 AI-native 世界里，我们说的是：意图的 originator ——无论是问题、功能还是产品——和 Claude 一起头脑风暴，再把结果写成 intent.md。我们往下走的每一步，都会形成所谓的 artifact chain。
So, in your project using Cursor, Claude, Code, Codex, whatever you want, you're just creating a folder called intent, and within that, that's where you're going to save your intent.md file. So, in my planning stage here, I might have a chat with my agent about adding dark mode as a feature, and I talk about what I want, how I want it to operate, and then we go and create an intent.md file from that.
先从 intent.md 开始，然后会有 spec，再往后还有别的文件。这就是在建立 artifact chain。在你的项目里，不管你用 Cursor、Claude Code、Codex 还是别的工具，你只要建一个叫 intent 的文件夹，然后把intent.md 保存在里面。
Then, I get the agent to save that as the intent.md file in the intent folder as proposed by Anthropic. And of course, with any of these artifacts, your team can do whatever they want in terms of a workflow. I think what's important here is that you start to standardize it and not chop and change it too often. That way, the team, the agents, the skills, all work on the same workflow, and you can grow from there. Now, once that intent.md file is created, it doesn't stop there.
所以在我的规划阶段，我可能会和 agent 聊给产品加 dark mode：我想要什么、希望它怎么工作，然后据此生成一份 intent.md。接着我让 agent 按 Anthropic 的建议，把文件存进 intent 文件夹。当然，这些 artifact 在团队工作流里可以按你们自己的方式处理。我认为重要的是你开始把它标准化，并且不要改得太勤。
It's It's suggested that the originator of the intent goes back over what the agent has written to correct anything and make sure that both of them are happy. Now, the person that creates this intent.md file is called the originator, and that doesn't have to be a specialist on the team. That can be anybody who wants to create the intent. It could be a customer who's putting in a bug request. It could be a product manager who has an idea for a feature.
这样团队、agent、skill 都在同一套工作流上工作，才能继续往上长。 intent.md 写完并不是结束。建议是：意图的 originator 再回头核对 agent 写的内容，纠正任何误解，确保双方都认可。创建这份 intent.md 的人叫 originator，这个人不一定是团队里的专家。可以是任何想创建意图的人。
It could be a developer who wants to capture a process improvement. So, you might have your own intent capture skill that produces something similar to this. What you might do over time as you're collecting more forms of intent, you might prefix the name of the intent before your intent.md file. This is something I've been doing myself and teach on my course. I call it discovery, not intent, but again, it's the same idea. So, the intent really can be captured by anyone.
可以是提交缺陷请求的客户，可以是有功能想法的产品经理，也可以是想记录一次流程改进的开发者。所以你可能有自己的 intent capture skill，产出类似这样的文件。随着你收集到更多形式的意图，你可能会在 intent.md 前面加上意图名称作为前缀。这是我自己一直在做、也在课程里教的做法。我把它叫 discovery，不叫 intent，但想法是一样的。
Could be a developer, uh a customer submitting a bug. They're basically just dropping their thoughts into this intent.md file. But then it is the product owner that should review these in the form of a backlog. These could simply be ordered files in a markdown file. All these ideas could be captured in Notion or Linear and then organized by either a product owner or in some cases I'll actually use my agents to triage the backlog of issues.
所以意图其实可以由任何人捕获。可以是开发者，也可以是提交缺陷的客户。他们基本上只是把自己的想法写进这份 intent.md。但随后应当由 product owner 以 backlog 的形式来审这些内容。它们可以只是 markdown 里按顺序排好的文件。