来源：https://academy.claude.com/courses/ai-native-sdlc-playbook/capture-intent 读这篇之前：01 导论 不确定：ZH 是 Clint 译官方英文课体，不是 Anthropic 中文。
本课词汇
| English | 中文 | 怎么记 |
|---|---|---|
| intent.md | 意图文件 | 要什么、为什么、边界。链的第一环 |
| proto-spec | 原型说明 | 还不是正式需求，但是人能读、下一阶段能吃 |
| originator | 提出的人 | 有想法的那个人，不一定是工程师 |
| product owner | 产品负责人 | 审 intent、决定进不进 Design |
| Cowork | Claude Cowork | 给非工程师用的 Claude 面 |
| leading indicator | 领先指标 | 过程快没快，现在就能看 |
| lagging indicator | 滞后指标 | 事后才知道有没有用 |
| survival rate | 存活率 | 多少份 intent 被产品负责人收下，而不是关掉 |
对照正文
意图从哪来 / Where intent enters
EN The intent.md, which kicks off the software development process, can enter through different routes. A person has an idea, a ticket is filed, or an incident is surfaced via an alert (see Stage 6: Maintain).
ZH intent.md 启动整个软件开发过程，入口可以不同：有人有个想法、提了工单，或告警把事故掀出来 （见 Stage 6: Maintain）。
EN When a person has an idea, they brainstorm with Claude and produce a Markdown proto-spec. In the traditional SDLC, the same person must then convince a member of the product team to write the idea up with them or on their behalf.
ZH 人有想法时，跟 Claude 一起头脑风暴，产出一份 Markdown 原型说明。传统 SDLC 里，同一个人还得说服产品团队的人一起写、或代写。
EN The proto-spec generated by Claude is human readable, version controlled, and immediately consumable by the next stage. The proto-spec is saved as an intent.md.
ZH Claude 生成的原型说明：人能读、进版本库、下一阶段立刻能用。存成 intent.md。
EN Regardless of whether the intent originates from an event trigger or a person, the same steps apply: the product owner reviews and corrects the agent-written intent.md before it is committed.
ZH 不管意图来自事件触发还是人，步骤一样：产品负责人在提交前审、改正 agent 写的 intent.md。
什么变了 / What changes
EN
| Traditional | AI-native |
|---|---|
| An idea passes through backlog entries, user stories, story points, and refinement meetings before anyone can act on it. Ownership transfers at each handoff, so what reaches engineering is several steps removed from what the originator meant. | The originator brainstorms with Claude and writes the result down as intent.md, a proto-spec in the originator’s own terms. The artifact contains what is wanted, why, and under which constraints. Repeat processes are encoded via skills. |
ZH
| 传统 | AI-native |
|---|---|
| 一个想法要过 backlog、用户故事、故事点和 refinement 会，才有人能动手。每次交接换主人，到工程手里已经跟提出者的意思隔了好几步。 | 提出者跟 Claude 头脑风暴，用自己的话说成 intent.md 这份原型说明。里面是要什么、为什么、边界是什么。重复流程用 skills 固化。 |
怎么起步 / Getting started
EN Prerequisites: None.
ZH 先决条件：无。
EN Infrastructure: Claude access for people who are not engineers (claude.ai or Cowork); an agreed intent.md template; a shared, version-controlled home for intent that the product owner watches. For a single product the simplest home is an intent/ folder in the product repo. This setup keeps the artifact chain next to the code derived from it. A dedicated intent repo is only worth the overhead when intent spans many repositories, and in a monorepo it is a directory. The Legacy systems section in Stage 3: Build covers how this home relates to a Jira or requirements tool that already holds the record.
ZH 基础设施：给非工程师的 Claude 入口（claude.ai 或 Cowork）；一份谈拢的 intent.md 模板；产品负责人盯着的、带版本的意图存放处。单产品最简单是产品仓库里的 intent/ 文件夹。这样工件链就挨着由它衍生的代码。只有意图跨很多仓库时，单独开 intent 仓库才划得来；在 monorepo 里它就是一个目录。Stage 3: Build 的遗留系统一节会讲这处存放跟已经当记录用的 Jira/需求工具怎么相处。
EN Setting this up is a one-time task for the platform or engineering team. A technical team member needs to stand up the intent home and decide who can write to it, since many contributors will come from across the organization.
ZH 搭这一套是平台或工程团队的一次性活。要有技术人员把意图存放处立起来，并决定谁能写，因为很多贡献者会来自组织各处。
EN Once the repository exists, contributors without Git experience don’t need to use Git directly. Instead a connector to the version-control system (e.g., GitHub) lets Claude commit Markdown files on their behalf from claude.ai or Cowork.
ZH 仓库有了之后，不会 Git 的人不必自己用 Git。连上版本库的连接器（例如 GitHub），让 Claude 从 claude.ai 或 Cowork 代他们提交 Markdown。
怎么做 / How to execute it
EN 1. The originator describes the problem to Claude in their own words. The originator may describe what they cannot do today, who is affected by the idea, what better looks like, or what is out of scope. No formal language is required.
2. Brainstorm until the idea is concrete. Claude asks the questions an analyst would ask: scope, users, constraints, and what success looks like.
3. Ask Claude to write the result as intent.md using the organization’s template, which can be encoded as a skill set up by a technical team member and signed off by a lead. This can cover the problem, proposed outcome, affected users and systems, constraints, and open questions.
4. The originator corrects anything Claude misunderstood.
5. Commit intent.md to the shared home. Author and timestamp join the record, and the product owner picks the idea up from there.
ZH 1. 提出者用自己的话跟 Claude 讲问题。可以讲今天做不到什么、想法影响谁、更好长什么样、什么不在范围内。不需要正式措辞。
2. 头脑风暴到想法具体为止。Claude 问分析师会问的：范围、用户、约束、成功长什么样。
3. 让 Claude 按组织模板写成 intent.md。模板可以做成 skill，由技术人员搭、负责人签字。可以覆盖问题、拟议结果、受影响的用户和系统、约束、未决问题。
4. 提出者改正 Claude 理解错的地方。
5. 把 intent.md 提交到共用存放处。作者和时间戳进入记录，产品负责人从那里接手。
长什么样 / What it looks like
EN intent.md:
ZH intent.md：
# Intent: claims status self-service
Author: J. Ortiz (claims operations). Status: draft.
## Problem
Customers phone the contact center to ask where their claim is.
Handlers spend roughly a third of call time on status-only queries.
## Proposed outcome
Customers see claim status, next step and expected date in the portal.
## Affected users and systems
Claims handlers, portal team, claims-core API.
## Constraints
No new PII in the portal session. Existing authentication only.
## Open questions
Do third-party loss adjusters need access too?ZH 官方示例，保持英文。理赔状态自助：问题、拟议结果、影响谁、约束、未决问题。
治理 / Governance considerations
EN The evidence is the committed intent.md, which lists the author, the timestamp, and the full revision history. It’s logged in the Git history of the intent home. The product owner approves, and the accept or reject decision that sends the intent into Stage 2: Design is recorded as the merge or the closing review.
ZH 证据就是提交进去的 intent.md：作者、时间戳、完整修订史。记在意图存放处的 Git 历史里。产品负责人批准；把意图送进 Stage 2: Design 的接受或拒绝，记成合并或关掉那次审查。
怎么衡量 / How to measure it
EN Leading indicator: Time from first conversation to a committed intent.md, read from Git history on the intent home, which records author and timestamp. The expectation is for this to fall from a multi-week elicitation and refinement cycle to hours.
ZH 领先指标：从第一次对话到提交 intent.md 的时间，从意图存放处 Git 历史读（上面有作者和时间戳）。预期从持续数周的访谈和 refinement，掉到几小时。
EN Lagging indicator: The survival rate, or the share of intent.md files that the product owner accepts into Stage 2: Design rather than closes. The accept or reject decision is recorded as the merge of the artifact or the closed review. Additionally, count the changes to intent.md made after the first spec.md commit for the same change.
ZH 滞后指标：存活率，也就是产品负责人收下送进 Stage 2: Design、而不是关掉的 intent.md 比例。接受或拒绝记成工件合并或关掉的审查。另外，数同一改动在第一份 spec.md 提交之后，又改了几次 intent.md。
读完能记住的三句话
EN Write what is wanted, why, and the constraints as intent.md before anyone starts a spec.
ZH 先写成 intent.md：要什么、为什么、边界是什么，再谈 spec。
EN The product owner reviews the agent-written file before it is committed. That review is the gate into Design. ZH 产品负责人在提交前审 agent 写的文件。这扇闸通向 Design。
EN Non-engineers do not need Git. Claude can commit Markdown from claude.ai or Cowork. ZH 非工程师不必会 Git。Claude 可以从 claude.ai 或 Cowork 代交 Markdown。