Capture as intent.md

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).作为软件开发流程起点的 intent.md，可以通过多种途径生成。它可以源于个人的想法、提交的工单，或是通过警报触发的事件（参见第 6 阶段：维护）。

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.当某人产生想法时，他们可以与 Claude 进行头脑风暴，并生成一份 Markdown 格式的初步规范（proto-spec）。在传统的软件开发生命周期（SDLC）中，此人必须说服产品团队成员共同撰写该想法，或者由对方代为撰写。

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.由 Claude 生成的初步规范不仅易于阅读，且支持版本控制，并可立即供下一阶段使用。该初步规范将保存为 intent.md 文件。

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.无论意图是源于事件触发还是个人想法，流程均相同：产品负责人需在 intent.md 提交前对其进行审核与修正。

What changes发生了什么变化

Getting started入门指南

• Prerequisites: None.先决条件：无。
• 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.基础设施：非工程人员需拥有 Claude 访问权限（claude.ai 或 Cowork）；需约定好 intent.md 模板；需一个由产品负责人监控的、共享且支持版本控制的意图存储库。对于单一产品，最简单的做法是在产品仓库中创建一个 intent/ 文件夹。这种设置可确保工件链与由其衍生的代码保持一致。仅当意图跨越多个仓库时，设立专门的意图仓库才具有成本效益；而在单体仓库（monorepo）中，将其作为目录即可。第 3 阶段“构建”中的“遗留系统”部分介绍了该存储库如何与已有的 Jira 或需求管理工具进行关联。

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.对于平台或工程团队而言，此项设置是一次性的工作。技术团队成员需建立意图存储库并确定写入权限，因为贡献者将来自组织内部的各个部门。

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.一旦仓库建立，不具备 Git 经验的贡献者无需直接操作 Git。他们可以通过版本控制系统（如 GitHub）的连接器，让 Claude 直接从 claude.ai 或 Cowork 代其提交 Markdown 文件。

How to execute it执行方法

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.发起人需用自己的语言向 Claude 描述问题。发起人可以描述当前无法实现的功能、受此想法影响的对象、理想的改进效果，或是超出范围的内容。无需使用正式术语。
2. Brainstorm until the idea is concrete. Claude asks the questions an analyst would ask: scope, users, constraints, and what success looks like.通过头脑风暴使想法具体化。Claude 会提出分析师通常会问的问题：范围、用户、约束条件以及成功的定义。
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.要求 Claude 使用组织的模板将结果编写为 intent.md。该模板可由技术团队成员设置为技能（skill），并由负责人签字确认。内容应涵盖问题、预期成果、受影响的用户和系统、约束条件以及待决问题。
4. The originator corrects anything Claude misunderstood.发起人对 Claude 理解有误的部分进行修正。
5. Commit intent.md to the shared home. Author and timestamp join the record, and the product owner picks the idea up from there.将 intent.md 提交至共享存储库。记录中会包含作者和时间戳，随后产品负责人将从此处接手该想法。

What it looks like示例形式

intent.md: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?

Governance considerations治理考量

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.已提交的 intent.md 即为证据，其中列出了作者、时间戳及完整的修订历史。这些信息会记录在意图存储库的 Git 历史中。产品负责人进行审批，而决定是否将意图推进至第 2 阶段“设计”的接受或拒绝决定，将作为合并操作或关闭评审记录下来。

How to measure it衡量指标

• 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.领先指标：从首次对话到提交 intent.md 所需的时间，可从意图存储库的 Git 历史中读取（记录了作者和时间戳）。预期目标是将耗时从数周的调研与细化周期缩短至数小时。
• 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.滞后指标：存活率，即产品负责人接受并推进至第 2 阶段“设计”的 intent.md 文件占比，而非关闭的文件。接受或拒绝的决定记录为工件的合并或关闭评审。此外，还需统计针对同一变更，在首次 spec.md 提交后对 intent.md 所做的修改次数。