{"@context":"https://schema.org","@type":"NewsArticle","generatedAt":"2026-08-21T18:41:23.743Z","headline":"AI 原生 SDLC 实战手册：Anthropic 如何用 Claude 重塑软件开发生命周期","description":"Anthropic 发布 AI 原生 SDLC 实战手册，提出将传统六阶段软件开发生命周期重构为 AI 嵌入各环节的闭环流程。手册指出，当代码不再是瓶颈时，规划、审查、部署等人速环节成为新约束，需通过 Claude 将需求压缩为 intent.md、以技能编码标准、用持续评测替代阶段门禁，并保留人工对关键代码的审查。 🔗 阅读原文 via AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","url":"https://www.aioga.com/news/cmt31oi0x0ehyro6tui3xycqe/","mainEntityOfPage":"https://www.aioga.com/news/cmt31oi0x0ehyro6tui3xycqe/","datePublished":"2026-08-21T14:28:27.000Z","dateModified":"2026-08-21T14:28:27.000Z","inLanguage":"zh-CN","publisher":{"@type":"NewsMediaOrganization","name":"Aioga","url":"https://www.aioga.com"},"citation":["https://claude.com/blog/the-ai-native-sdlc-playbook","https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe"],"canonicalUrl":"https://www.aioga.com/news/cmt31oi0x0ehyro6tui3xycqe/","directAnswer":{"@type":"Answer","text":"Anthropic 发布 AI 原生软件开发生命周期手册，主张把 AI 嵌入规划、设计、构建、测试、部署和维护六个阶段。材料认为，代码生成提速后，审批、审查、交接及安全检查等人工作业可能成为新的约束。","url":"https://www.aioga.com/news/cmt31oi0x0ehyro6tui3xycqe/","dateCreated":"2026-08-21T14:28:27.000Z","author":{"@type":"Organization","@id":"https://www.aioga.com/authors/aioga-editorial/#editorial-team","name":"Aioga Editorial Team","url":"https://www.aioga.com/authors/aioga-editorial/"}},"evidence":[{"@type":"CreativeWork","name":"Claude：Blog（网页 source article","url":"https://claude.com/blog/the-ai-native-sdlc-playbook","datePublished":"2026-08-21T14:28:27.000Z","provider":{"@type":"Organization","name":"Claude：Blog（网页","url":"https://claude.com/blog/the-ai-native-sdlc-playbook"}},{"@type":"CreativeWork","name":"AIHot archive record","url":"https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","datePublished":"2026-08-21T14:28:27.000Z","provider":{"@type":"Organization","name":"AIHot","url":"https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe"}}],"aggregationSource":"Claude：Blog（网页","originalPublisher":{"name":"Claude：Blog（网页","url":"https://claude.com/blog/the-ai-native-sdlc-playbook"},"geoDeepAnswer":null,"article":{"id":"cmt31oi0x0ehyro6tui3xycqe","slug":"cmt31oi0x0ehyro6tui3xycqe","url":"https://www.aioga.com/news/cmt31oi0x0ehyro6tui3xycqe/","title":"AI 原生 SDLC 实战手册：Anthropic 如何用 Claude 重塑软件开发生命周期","title_en":"","summary":"Anthropic 发布 AI 原生 SDLC 实战手册，提出将传统六阶段软件开发生命周期重构为 AI 嵌入各环节的闭环流程。手册指出，当代码不再是瓶颈时，规划、审查、部署等人速环节成为新约束，需通过 Claude 将需求压缩为 intent.md、以技能编码标准、用持续评测替代阶段门禁，并保留人工对关键代码的审查。 🔗 阅读原文 via AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","source":"Claude：Blog（网页","sourceUrl":"https://claude.com/blog/the-ai-native-sdlc-playbook","aiHotUrl":"https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","publishedAt":"2026-08-21T14:28:27.000Z","category":"行业动态","score":72,"selected":true,"articleBody":["How to transform your software development lifecycle with AI—stage by stage.","Organizations have started using AI to write code at a speed unthinkable one year ago, yet the processes around the code haven't changed at the same pace.","Many engineering teams still have the same approval gates, reviews, handoffs, and policies, stalling productivity gains made by using agentic coding solutions like Claude Code：https://claude.com/product/claude-code.","The software development lifecycle (SDLC) is the process that takes software from idea to production. Most organizations run some version of the same six stages, covering planning, design, building, testing, deploying, and maintaining software. Traditionally, each stage is a discrete phase owned by a different role. Product managers write requirements, technical architects turn them into designs, engineers build the designs, QA teams at regulated enterprises verify it, releases teams ship it, and operations monitors what is running. Work moves between the phases through documents, tickets, and sign-offs.","The traditional software development lifecycle (SDLC) is process-heavy to ensure accountability and control at each step. However, the traditional SDLC was designed to maximize efficiency in an era where the most time-consuming and expensive stage was writing and implementing code, which is no longer the case. PRDs, estimation rituals, and product security reviews all existed to force alignment during what could be weeks, months, or quarters of development work.","The traditional SDLC also features controls that assume every step is performed by humans. The organizations generating the most value have rebuilt their process around what agentic AI can now do, while ensuring that humans stay in the loop. In this guide, we walk through several of our Applied AI team's best practices for integrating Claude internally across each stage of the SDLC to accelerate development and make processes run faster, inspired by working with our customers.","When code is no longer the bottleneck and the build phase runs faster than the traditional SDLC allows for, three things become true:","Let's use a security bottleneck as an example. Security teams are sized for human output, so when agents multiply code output, either the review queue builds or code ships under-reviewed. A regulated organization can't accept either outcome, so its security and policy checks have to keep pace with the agents.","To better realize the productivity gains of and secure agentic AI, the traditional SDLC lifecycle requires the same level of transformation as the implementation phase has undergone.","The AI-native SDLC is a reimagined process that combines the old control objectives with new enforcement. Instead of a linear flow, the process becomes a loop, and AI is embedded at each point. The AI-native SDLC promotes automated handover and triggering of subsequent plays, helping to address the manual and clunky nature of handoff between the phases of the traditional SDLC.","The table below highlights the ends of the spectrum between traditional SDLC and AI-native SDLC, supported by Claude. Most organizations sit somewhere between the two columns.","The thread running through the right-hand column is the committed artifact. Each stage ends by writing one to version control (including intent.md , spec.md , plan.md , the diff and its tests, the PR with its review findings, and the incident record) and the next stage begins by reading it. For the early stages, .md files are the predominant artifact because a product owner and an agent can both read and act on the same file. From Build onward, the artifact is code and its records. The chain of commits is also the audit trail: who asked for what, what the agent produced, and who approved it.","Humans remain accountable for every decision that requires judgment. In the agentic SDLC world, the human attention shifts along with the artifacts that must be reviewed.","The plays are the core of the playbook and are grouped into six non-linear stages (Plan, Design, Build, Test, Deploy, Maintain), which together cover the complete lifecycle.","These steps are modular and organizations may choose to prioritize transforming different stages at different times based on their unique needs. Each play names its dependencies under \"Prerequisites,\" which the dependency graph further illustrates.","A stage ends by committing an artifact with the commit initiating the next stage. An accepted intent.md triggers the requirements and design pass, an approved spec.md triggers plan mode, a merged PR triggers the pipeline, and a breached control band in production writes the next intent.md and so the loop continues.","First, you prompt each step by hand with the end state being a loop in which each accepted artifact fires the next gate. Human attention concentrates at the gates, reviewing what the agent flagged rather than starting each stage from scratch.","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: Maintenance).","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.","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 .","Regardless of whether the intent originates from an event trigger or an agent, the same steps apply: the product owner reviews and corrects the agent-written intent.md before it is committed.","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.","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.","Once approved by the product owner, Claude takes the accepted intent.md and produces a requirements and design spec. This is guided by the organization's skills：https://code.claude.com/docs/en/skills for brand, security, compliance, and UX.","The product owner reviews that spec, but doesn't write it. The goal of this process is to create a spec the engineering team can plan against, with flagged areas of concern.","Instead of being discovered in a review weeks later, the live policy is read and applied while the spec is written. The organization's skills are applied as constraints on the spec. The spec, the prompt that produced it, and the skill versions in force are all logged in version control. The product owner signs off the spec, and routes flagged concerns to the named policy owners.","Engineers start Claude Code sessions in plan mode：https://code.claude.com/docs/en/permission-modes, give Claude the approved spec.md from Stage 2: Design, and let it interview them, iterating on the plan until the engineer is happy with it.","Design review happens before any code is generated, when changing course is still a matter of editing a document. Plan mode enforces this itself, since Claude cannot edit files until the engineer accepts the plan. The plan and its revisions are logged along with who accepted it. Routine changes are approved by the engineer, and anything the organization classes as higher risk goes to a tech lead or architect.","Claude Code can also run in auto mode, where the engineer approves the plan and, once happy and iterated upon, Claude applies each change without a per-edit prompt. As the guardrails from the later plays mature (a tuned CLAUDE.md , skills that encode policy, hooks that block unsafe actions, and a test suite Claude can run), auto-accept becomes the default for routine work: a tight spec.md , a small blast radius, and code the tests already cover.","The shift is now away from the user watching the agent make the edits and reviewing actions, towards the review of artifacts after longer autonomous sessions. Auto-accept mode further enables parallelism across individuals and the team when used with worktrees and is fundamental to running the SDLC autonomously and closing the loop as described in Stage 6: Maintenance.","CLAUDE.md ：https://code.claude.com/docs/en/memory gives Claude the context a new joiner would need, covering conventions, commands, architecture, and the mistakes the team sees most often. Knowledge that used to sit in people's heads and on wikis becomes a file the agent reads at the start of every session, maintained by the whole team and iterated on whenever a mistake is made.","CLAUDE.md is version controlled, so the instructions the agent works to are reviewable and auditable. Team conventions are applied through the file, changes to it are logged in git history, and code owners approve those changes in PR review.","Skills are how an organization makes its institutional knowledge operational. The instructions are explicit, version-controlled, applied broadly, and updated centrally when policy changes. The rule of thumb: write a skill for institutional knowledge that must be applied consistently; don't write a skill for components that belong in CLAUDE.md or a prompt.","A skill is a control, though an advisory one. It makes Claude likely to apply the policy while the code is written, and nothing forces a session to comply with it. A policy that must always hold needs something deterministic behind the skill, such as a hook that blocks the action or a review pass that re-checks the policy at the PR. The skill makes violations rare and the hook makes them close to impossible. Skill invocations are logged in session traces, and the policy owner reviews skill changes like code.","A skill is an advisory control while a hook：https://code.claude.com/docs/en/hooks is the deterministic layer behind it. Most of Claude's actions are file edits and shell commands during implementation, so the build phase is where hooks can end up firing most often.","Back any skill whose policy has to hold without exception. A hook runs on each action that matches it, so build-phase hooks should be fast and scoped to the file that changed. Heavier checks such as the full test suite belong at the commit or the PR.","A hook that asks a human for approval belongs with the gates in Stage 5: Deploy, because an approval prompt during the build puts a person back on the critical path of all the sessions running in parallel.","One engineer can drive several streams of work at once.","A parallel session is another full Claude Code instance, working a separate task in its own git worktree：https://code.claude.com/docs/en/worktrees. Each independent session knows nothing about the others, and the engineer steering them is the only thing they share.","A subagent：https://code.claude.com/docs/en/sub-agents runs inside a single session as a scoped helper with its own context window and tool limits and suits jobs that recur in multiple tasks such as verifying the app runs as expected.","Parallel sessions raise the number of tasks an engineer can have in flight, while subagents keep each session focused on its own task. The engineer's job is steering and reviewing all of them.","More sessions means more output, so the controls have to come from configuration in the repo. Hooks and permission settings there apply to all sessions, and what a session does is logged and attributed to the engineer who ran it.","Always give Claude a way to verify its own work, whether tests, a build, or a screenshot diff. A session checks its own work and fixes its own mistakes before an engineer sees them.","The feedback loop should not be confused with a verifier subagent (Stage 3: Build). The feedback loop runs through the whole task as many times as the work. The verifier subagent, on the other hand, is one way to package the final check by running a fresh context window once the session believes the work is done. This way the verdict is not colored by the assumptions that produced the code.","Evals are the AI-native equivalent of stage-gate QA. In practice that means a suite that runs whenever the agent's configuration changes. When a new model is swapped in or a prompt is rewritten, the eval suite says whether the agent still does the work to the same standard.","The evals should be seen as a live suite. As models improve, cases that once discriminated stop doing so and new ones must be added that arise from ongoing monitoring.","Depending on the use case, some teams may prefer to run these evals offline on a set cadence rather than on every change. The steps below are for continuous evaluations.","Evals give QA a gate that keeps up with agent output. The pass-rate threshold is enforced as a merge check, runs are logged so results can be compared over time, and the team that owns the configuration change approves it.","Claude both gives and receives reviews. It reviews incoming PRs against the organization's policies and addresses review comments on its own PRs. This allows engineers to focus on behavior in their PR review, which boils down to judging intent and risk.","Separation of duties is preserved, because the agent that wrote the code has no way to approve it. The review policy in REVIEW.md is applied to all PRs, and findings, fixes, ratings and approvals are logged in the PR history, so the PR is the audit record. Approval comes from a human through branch protection, informed by the findings.","The build phase used hooks as guardrails, allowing or blocking actions with no human involved (Stage 3: Build). A hook can also ask, pausing the action until a specific person approves, which is what release gating needs.","The play sits in Stage 5: Deploy because the release gate is the clearest case, but hooks are not deploy-specific: they run wherever Claude acts. For example, hooks can block edits to migrations and infra without a change ticket during Stage 3: Build, and stop the agent editing test files during a fix task in Stage 4: Test.","Hooks are the approval gates. The gate condition is enforced every time, for everyone. Allow and block decisions are logged with a timestamp. The gate also defines what counts as approval, whether that's an approved change ticket or the release manager's sign-off.","Run Claude Code non-interactively inside the CI/CD pipeline, sandbox the execution so long-running agents run safely, expose deployment through MCP integrations, and rehearse the rollback paths before the agent ever needs them.","The governing principle is that the agent may act up to the production gate and cannot pass it. The controls below enforce this principle.","So far, we've discussed how to add Claude to each stage of the SDLC process, with each stage requiring a human to launch the initial steps. This stage, however, shifts the focus to autonomous running of Claude to close the loop.","For example, a continuously running monitoring agent could, off the back of a bug ticket being raised, create an intent.md , and flow through the requirements, plan, build test and review phases. Stage 6: Maintenance runs headless, with an independent confidence gate between stages, a deterministic check or an adversarial reviewing agent, deciding whether the previous stage's output continues or is escalated to a human.","A deterministic script watches production and invokes Claude when a control band is breached. Monitoring of a breach is a helpful example of the pattern for the loop running autonomously, while the Claude Tag：https://claude.com/product/tag (public beta) section at the end of the stage covers work arriving through different channels.","The tier boundaries are enforced from version-controlled config, with permissions and managed settings denying production access. Invocations, findings and triage decisions are logged with a timestamp. A service owner triages and approves findings, resulting changes go through the normal PR review gate, and the runbooks the agent may trigger were approved in advance."],"articleImages":[{"sourceUrl":"https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6903d222061abf091318fb82_423062049d4676b41d52b16068cbb5e21603190e-1000x1000.svg","alt":"","afterParagraph":0,"url":"/media/articles/cmt31oi0x0ehyro6tui3xycqe/4fa65b004ebab739.jpg"},{"sourceUrl":"https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6a8739a1b934ffe55bfc9715_44592f18.png","alt":"","afterParagraph":6,"url":"/media/articles/cmt31oi0x0ehyro6tui3xycqe/961cec5ccc0c095f.png"},{"sourceUrl":"https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6a8858c2eccce183e7553cf2_53b010df.png","alt":"","afterParagraph":9,"url":"/media/articles/cmt31oi0x0ehyro6tui3xycqe/e48b816007d61220.png"},{"sourceUrl":"https://cdn.prod.website-files.com/68a44d4040f98a4adf2207b6/6a8855c75344623fc81efcb8_5d5a3c05.png","alt":"","afterParagraph":16,"url":"/media/articles/cmt31oi0x0ehyro6tui3xycqe/0e2db4f667c1f938.png"}],"mediaStatus":"ok","articleBodyZh":["如何利用AI逐步改造您的软件开发生命周期。","组织已经开始使用AI以一年以前难以想象的速度编写代码，但围绕代码的流程并没有以同样的速度改变。","许多工程团队仍然保持着相同的审批关卡、评审、交接和政策，这拖慢了使用像Claude Code（https://claude.com/product/claude-code）这样的自主编码解决方案所带来的生产力提升。","软件开发生命周期（SDLC）是将软件从构想到生产的过程。大多数组织运行某种版本的相同六个阶段，涵盖计划、设计、构建、测试、部署和维护软件。传统上，每个阶段都是由不同角色负责的独立环节。产品经理撰写需求，技术架构师将其转化为设计，工程师构建设计方案，受监管企业的QA团队进行验证，发布团队发布软件，而运维团队监控运行情况。各阶段之间的工作通过文档、工单和签核进行流转。","传统的软件开发生命周期（SDLC）流程繁重，以确保每个步骤的责任和控制。然而，传统SDLC的设计初衷是为了在编写和实施代码是最耗时、最昂贵的阶段的时代最大化效率，而现在情况已经不同。PRD（产品需求文档）、估算流程和产品安全评审都存在的目的是在可能持续数周、数月甚至数个季度的开发工作期间强制对齐。","传统SDLC还具有假设每一步都是由人类执行的控制措施。创造最大价值的组织已经围绕自主AI可以完成的工作重建了流程，同时确保人为环节仍然存在。在本指南中，我们将介绍应用AI团队在SDLC各阶段内部整合Claude的若干最佳实践，以加速开发并让流程运行更快，灵感来源于我们与客户的合作经验。","当代码不再是瓶颈，构建阶段的运行速度超过传统SDLC允许的速度时，有三件事将变为现实：","让我们用安全瓶颈作为例子。安全团队的规模是为人类产出而设的，因此当代理人增加代码产出时，要么审查队列积压，要么代码未经充分审查就发布。受监管的组织无法接受这两种结果，因此其安全和政策检查必须跟上代理人的节奏。","为了更好地实现代理型 AI 的生产力提升并确保安全，传统的软件开发生命周期（SDLC）需要像实施阶段那样进行同等水平的变革。","AI 原生 SDLC 是一个重新构想的流程，它将旧的控制目标与新的执行手段结合起来。流程不再是线性流动，而是变成循环，并且 AI 嵌入到每一个环节。AI 原生 SDLC 促进了自动化交接和后续操作的触发，有助于应对传统 SDLC 各阶段之间手动且笨重的交接问题。","下表突出显示了传统 SDLC 与 AI 原生 SDLC 之间的光谱两端，由 Claude 支持。大多数组织介于两列之间的某个位置。","右列的一条主线是提交的工件。每个阶段的结束都通过写入版本控制（包括 intent.md、spec.md、plan.md、差异及其测试、PR 及其审查结果和事件记录）来完成，而下一个阶段则以读取它开始。在早期阶段，.md 文件是主要工件，因为产品负责人和代理人都可以读取并在同一个文件上进行操作。从构建阶段开始，工件就是代码及其记录。提交链也是审计轨迹：是谁提出了什么需求，代理人产出什么，以及谁批准了它。","人类仍然要对每一个需要判断的决策负责。在代理型 SDLC 世界中，人类的注意力会随着必须审查的工件转移。","这些“操作步骤”是操作手册的核心，被分为六个非线性阶段（计划、设计、构建、测试、部署、维护），共同涵盖整个生命周期。","这些步骤是模块化的，组织可以根据其独特需求选择在不同时间优先改造不同阶段。每个操作步骤在“先决条件”下列出其依赖关系，依赖图进一步说明这些关系。","一个阶段通过提交一个工件来结束，而该提交会启动下一个阶段。一个被接受的 intent.md 会触发需求和设计阶段，一个被批准的 spec.md 会触发计划模式，一个合并的 PR 会触发流水线，而生产中违反控制带的情况会写下下一个 intent.md，从而循环继续。","首先，你需要手动提示每一步，最终状态是一个循环，每个被接受的工件都会触发下一个关卡。人的注意力集中在这些关卡上，审查代理标记的内容，而不是从头开始启动每个阶段。","启动软件开发过程的 intent.md 可以通过不同的途径进入。一个人有了想法，会提交工单，或者通过警报发现一个事件（参见阶段 6：维护）。","当一个人有了想法时，他们会与 Claude 头脑风暴，并生成一个 markdown 原型规范。在传统的 SDLC 中，同一个人必须说服产品团队的成员与自己一起撰写该想法，或代表他们来撰写。","Claude 生成的原型规范是人类可读的、受版本控制的，并且可以立即被下一个阶段使用。该原型规范被保存为 intent.md。","无论 intent 是来源于事件触发还是代理生成，其步骤都相同：产品负责人会在提交前审查并修改代理编写的 intent.md。","设置这个流程是平台或工程团队的一次性任务。技术团队成员需要建立 intent home 并决定谁可以向其中写入，因为许多贡献者将来自整个组织。","一旦仓库存在，没有 git 经验的贡献者就不需要直接使用 git。相反，连接到版本控制系统（例如 GitHub）的连接器可以让 Claude 代表他们从 claude.ai 或 Cowork 提交 Markdown 文件。","证据就是提交的 intent.md，它列出了作者、时间戳和完整的修订历史。它记录在 intent home 的 git 历史中。产品负责人批准后，将 intent 送入阶段 2：设计的接受或拒绝决定会被记录为合并或关闭审查。","一旦产品负责人批准，Claude 会根据被接受的 intent.md 制作需求和设计规范。这一过程受组织技能的指导：https://code.claude.com/docs/en/skills，包括品牌、安全、合规和用户体验（UX）。","产品负责人会审查该规范，但不会撰写它。该流程的目标是创建工程团队可依据进行计划的规范，并标记出需要关注的区域。","在几周后的审查中发现问题之前，实时政策会在规范编写过程中被读取和应用。组织技能作为约束应用于规范。规范、生成规范的提示以及生效的技能版本都会被记录在版本控制中。产品负责人签署规范，并将标记的关注事项传达给指定的政策所有者。","工程师在计划模式下启动 Claude Code 会话：https://code.claude.com/docs/en/permission-modes，向 Claude 提供第二阶段设计中的已批准 spec.md，让其进行访谈，并在工程师满意前不断迭代计划。","设计评审在任何代码生成之前进行，此时更改方向仍然只是编辑文档而已。计划模式本身强制执行这一点，因为 Claude 在工程师接受计划前无法编辑文件。计划及其修订记录会与接受者信息一同记录。常规更改由工程师批准，而组织认定的高风险更改则交给技术负责人或架构师处理。","Claude Code 还可以在自动模式下运行，即工程师批准计划后，一旦满意并完成迭代，Claude 可以不依赖每次编辑提示地应用每个更改。随着后续环节的护栏逐步完善（经过调优的 CLAUDE.md、编码政策的技能、阻止不安全操作的钩子，以及 Claude 可以运行的测试套件），自动接受模式成为例行工作的默认模式：紧凑的 spec.md、小范围影响、以及已有测试覆盖的代码。","工作重心现在从用户实时监控代理进行编辑及审核操作，转向更长时间的自主会话后的成果物审查。结合工作树使用时，自动接受模式进一步实现个人和团队的并行操作，并且是实现 SDLC 自主运行及闭环流程（如第六阶段：维护中描述）的基础。","CLAUDE.md：https://code.claude.com/docs/en/memory 为 Claude 提供新加入成员所需的上下文，涵盖规范、命令、架构以及团队最常见的错误。以前存储在人员脑海和维基上的知识，现在变成了一个在每次会话开始时由代理读取的文件，由整个团队维护，并在出现错误时进行迭代。","CLAUDE.md 是版本控制的，因此代理遵循的指令是可审查和可追溯的。团队规范通过该文件应用，对文件的更改记录在 git 历史中，代码所有者在 PR 审查中批准这些更改。","技能是组织使其制度化知识可操作化的方式。这些指令是明确的、版本控制的、广泛应用的，并在政策变更时集中更新。经验法则：为必须一致应用的制度化知识编写技能；不要为属于 CLAUDE.md 或提示的组件编写技能。","技能是一种控制，但属于建议性控制。它使 Claude 在代码编写时更可能遵循政策，但不会强制会话必须遵守。必须始终保持的政策需要技能背后有确定性机制，例如阻止操作的钩子或在 PR 时重新检查政策的审查流程。技能使违规行为罕见，而钩子使其几乎不可能发生。技能调用会记录在会话跟踪中，政策所有者像审查代码一样审查技能更改。","技能是一种建议性控制，而钩子：https://code.claude.com/docs/en/hooks 是其背后的确定性层。Claude 执行的大部分操作是在实现过程中进行文件编辑和 shell 命令，因此构建阶段是钩子最常触发的环节。","支持任何必须无例外遵循其政策的技能。钩子会在匹配其条件的每个操作上运行，因此构建阶段的钩子应快速且限定在发生变更的文件上。较重的检查，例如完整测试套件，应放在提交或 PR 阶段。","要求人工批准的钩子应放在第 5 阶段：部署的关卡中，因为构建阶段的批准提示会让人重新成为所有并行会话的关键路径。","一名工程师可以同时推动多个工作流。","并行会话是另一个完整的 Claude 代码实例，在其自己的 git 工作树中处理一个独立任务：https://code.claude.com/docs/en/worktrees。每个独立的会话彼此之间互不知情，唯一共享的是操作它们的工程师。","子代理：https://code.claude.com/docs/en/sub-agents 在单个会话内运行，作为具有自己上下文窗口和工具限制的作用域助手，适用于在多个任务中重复出现的工作，例如验证应用是否按预期运行。","并行会话增加了工程师可以同时处理的任务数量，而子代理则保持每个会话专注于自身任务。工程师的工作是引导和审查所有会话。","更多的会话意味着更多的输出，因此需要通过仓库中的配置来进行控制。那里设置的钩子和权限适用于所有会话，会话所做的任何操作都会被记录，并归属于运行它的工程师。","始终为 Claude 提供验证自身工作的方式，无论是测试、构建还是截图差异。会话会在工程师看到之前检查自己的工作并修正自己的错误。","反馈循环不应与验证子代理（阶段 3：构建）混淆。反馈循环会贯穿整个任务，运行的次数与工作量相同。另一方面，验证子代理是一种通过在会话认为工作完成后运行一个新上下文窗口来进行最终检查的方式。这样，判定不会因为生成代码时的假设而受到影响。","评估是 AI 原生的阶段门质量保证（stage-gate QA）等价物。在实践中，这意味着每当代理配置更改时都会运行一套测试。每当新的模型被替换或提示被重写时，评估套件会判断代理是否仍然按照同样的标准完成工作。","评估应被视为一个实时套件。随着模型的改进，曾经能够区分情况的测试用例不再有效，需要添加新的测试用例，这些用例基于持续的监控生成。","根据使用场景，某些团队可能更倾向于按固定周期离线运行这些评估，而不是在每次更改时运行。以下步骤适用于持续评估。","评估为 QA 提供了一个与代理输出保持同步的门控。通过合并检查来执行通过率阈值，运行结果会被记录以便随时间比较，并且拥有配置变更的团队会批准它。","Claude 既提供也接受评审。它根据组织的政策审查进来的 PR，并对它自己 PR 的评审意见进行响应。这使得工程师可以专注于在 PR 审查中评估行为，最终归结为判断意图和风险。","职责分离得以保持，因为编写代码的代理无法批准它。REVIEW.md 中的审查政策适用于所有 PR，发现、修复、评级和批准都会记录在 PR 历史中，因此 PR 本身就是审计记录。批准通过人类在分支保护下进行，并依据发现结果作出决策。","构建阶段使用了钩子作为护栏，在无人参与的情况下允许或阻止操作（阶段 3：构建）。钩子还可以提出请求，暂停操作直到特定人员批准，这正是发布门控所需的。","该操作位于阶段 5：部署，因为发布门是最明显的例子，但钩子并非部署特定：它们在 Claude 执行的任何地方都运行。例如，在阶段 3：构建期间，如果没有变更单，钩子可以阻止对迁移和基础设施的编辑；在阶段 4：测试的修复任务中，可阻止代理编辑测试文件。","钩子即审批门控。每次都会对所有人强制执行门控条件。允许和阻止的决定会带时间戳记录。门控还定义了什么算作批准，无论是已批准的变更单还是发布经理的签字。","在 CI/CD 流水线中以非交互方式运行 Claude 代码，对执行进行沙箱隔离以保证长期运行的代理安全，通过 MCP 集成暴露部署，并在代理实际需要前演练回滚路径。","基本原则是代理可以执行到生产门控，但不能通过它。下面的控制措施执行这一原则。","到目前为止，我们讨论了如何将 Claude 添加到 SDLC 流程的每个阶段，每个阶段都需要人类启动初始步骤。然而，本阶段将重点转向 Claude 的自主运行以闭环整个流程。","例如，一个持续运行的监控代理可以在一个错误工单被提出后，创建一个 intent.md，并流转通过需求、计划、构建、测试和审核阶段。第六阶段：维护阶段以无头模式运行，在各阶段之间有独立的可信度门，一个确定性检查或对抗性审核代理，决定前一阶段的输出是继续执行还是升级给人工处理。","一个确定性脚本监控生产环境，并在控制带被突破时调用 Claude。监控违规是循环自主运行模式的一个有益示例，而在阶段末尾提到的 Claude Tag：https://claude.com/product/tag（公开测试版）部分，涵盖了通过不同渠道到达的工作内容。","版本控制的配置实施了等级边界，权限和托管设置拒绝生产访问。调用、发现和分类决策都会记录时间戳。服务负责人对发现进行分类和批准， resulting changes 会经过正常的 PR 审核门，而代理可能触发的运行手册则已事先获得批准。"],"translationStatus":"translated","bodyOrigin":"source-page","editorial":{"summary":"Anthropic 发布 AI 原生软件开发生命周期手册，主张把 AI 嵌入规划、设计、构建、测试、部署和维护六个阶段。材料认为，代码生成提速后，审批、审查、交接及安全检查等人工作业可能成为新的约束。","background":"传统 SDLC 通过文档、工单和签字在不同角色之间推进工作，其流程设计建立在代码编写和实现最耗时的前提上。Anthropic 表示，部分组织正围绕代理式 AI 重建流程，同时保留人在关键环节的参与。","viewpoint":"Aioga 判断，这份手册的重点不是单纯提高代码产量，而是重新评估与代理式开发匹配的流程控制。将需求压缩为 intent.md、以技能编码标准并采用持续评测，可能改变团队的协作接口，但材料未证明这些做法已普遍验证。","implications":"当代理式工具提高代码产出后，安全团队、审查队列和政策检查可能面临处理能力不足的问题。对受监管组织而言，放大代码生成能力并不等于可以减少控制；审查机制是否能同步扩展，将影响提速能否转化为实际交付效率。","nextStep":"值得关注 Anthropic 后续是否提供不同组织规模、监管环境和项目类型下的实施证据，以及持续评测、人工审查和安全检查如何具体衔接。材料目前只说明方向与实践建议，不能据此推断明确的效率提升幅度或普适结果。","evidenceRefs":["title","summary","articleBody","source"],"status":"published","aiGenerated":true,"autoApproved":true,"generatedBy":"aioga-editorial:gpt-5.6-sol","reviewedBy":"aioga-editorial-review:gpt-5.6-sol","generatedAt":"2026-08-21T14:43:59.139Z","sourceHash":"218009a210a549fa","review":{"approved":true,"groundedness":94,"clarity":93,"duplicationRisk":12,"blockingIssues":[],"notes":["“Aioga 判断”已明确标注为观点，未冒充来源事实。","“材料未证明这些做法已普遍验证”“不能据此推断明确的效率提升幅度或普适结果”等表述属于审慎限定，与来源材料的证据范围相符。","“部分组织正围绕代理式 AI 重建流程”可更严格表述为“来源称，创造最大价值的组织已围绕代理式 AI 重建流程”，但不影响事实审核结论。"]},"validation":{"passed":true,"mode":"ai-auto","revisions":0,"checks":["schema","length","source-attribution","low-source-overlap","no-html","independent-ai-review"]}},"tags":["行业动态","Claude：Blog（网页）"],"translations":{"zh-CN":{"title":"AI 原生 SDLC 实战手册：Anthropic 如何用 Claude 重塑软件开发生命周期","summary":"Anthropic 发布 AI 原生 SDLC 实战手册，提出将传统六阶段软件开发生命周期重构为 AI 嵌入各环节的闭环流程。手册指出，当代码不再是瓶颈时，规划、审查、部署等人速环节成为新约束，需通过 Claude 将需求压缩为 intent.md、以技能编码标准、用持续评测替代阶段门禁，并保留人工对关键代码的审查。 🔗 阅读原文 via AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"AI 原生 SDLC 实战手册：Anthropic 如何用 Claude 重塑软件开发生命周期 - Aioga AI资讯","description":"Anthropic 发布 AI 原生 SDLC 实战手册，提出将传统六阶段软件开发生命周期重构为 AI 嵌入各环节的闭环流程。手册指出，当代码不再是瓶颈时，规划、审查、部署等人速环节成为新约束，需通过 Claude 将需求压缩为 intent.md、以技能编码标准、用持续评测替代阶段门禁，并保留人工对关键代码的审查。 🔗 阅读原文 via AIHOT · h...","url":"https://www.aioga.com/news/cmt31oi0x0ehyro6tui3xycqe/","articleBody":["如何利用AI逐步改造您的软件开发生命周期。","组织已经开始使用AI以一年以前难以想象的速度编写代码，但围绕代码的流程并没有以同样的速度改变。","许多工程团队仍然保持着相同的审批关卡、评审、交接和政策，这拖慢了使用像Claude Code（https://claude.com/product/claude-code）这样的自主编码解决方案所带来的生产力提升。","软件开发生命周期（SDLC）是将软件从构想到生产的过程。大多数组织运行某种版本的相同六个阶段，涵盖计划、设计、构建、测试、部署和维护软件。传统上，每个阶段都是由不同角色负责的独立环节。产品经理撰写需求，技术架构师将其转化为设计，工程师构建设计方案，受监管企业的QA团队进行验证，发布团队发布软件，而运维团队监控运行情况。各阶段之间的工作通过文档、工单和签核进行流转。","传统的软件开发生命周期（SDLC）流程繁重，以确保每个步骤的责任和控制。然而，传统SDLC的设计初衷是为了在编写和实施代码是最耗时、最昂贵的阶段的时代最大化效率，而现在情况已经不同。PRD（产品需求文档）、估算流程和产品安全评审都存在的目的是在可能持续数周、数月甚至数个季度的开发工作期间强制对齐。","传统SDLC还具有假设每一步都是由人类执行的控制措施。创造最大价值的组织已经围绕自主AI可以完成的工作重建了流程，同时确保人为环节仍然存在。在本指南中，我们将介绍应用AI团队在SDLC各阶段内部整合Claude的若干最佳实践，以加速开发并让流程运行更快，灵感来源于我们与客户的合作经验。","当代码不再是瓶颈，构建阶段的运行速度超过传统SDLC允许的速度时，有三件事将变为现实：","让我们用安全瓶颈作为例子。安全团队的规模是为人类产出而设的，因此当代理人增加代码产出时，要么审查队列积压，要么代码未经充分审查就发布。受监管的组织无法接受这两种结果，因此其安全和政策检查必须跟上代理人的节奏。","为了更好地实现代理型 AI 的生产力提升并确保安全，传统的软件开发生命周期（SDLC）需要像实施阶段那样进行同等水平的变革。","AI 原生 SDLC 是一个重新构想的流程，它将旧的控制目标与新的执行手段结合起来。流程不再是线性流动，而是变成循环，并且 AI 嵌入到每一个环节。AI 原生 SDLC 促进了自动化交接和后续操作的触发，有助于应对传统 SDLC 各阶段之间手动且笨重的交接问题。","下表突出显示了传统 SDLC 与 AI 原生 SDLC 之间的光谱两端，由 Claude 支持。大多数组织介于两列之间的某个位置。","右列的一条主线是提交的工件。每个阶段的结束都通过写入版本控制（包括 intent.md、spec.md、plan.md、差异及其测试、PR 及其审查结果和事件记录）来完成，而下一个阶段则以读取它开始。在早期阶段，.md 文件是主要工件，因为产品负责人和代理人都可以读取并在同一个文件上进行操作。从构建阶段开始，工件就是代码及其记录。提交链也是审计轨迹：是谁提出了什么需求，代理人产出什么，以及谁批准了它。","人类仍然要对每一个需要判断的决策负责。在代理型 SDLC 世界中，人类的注意力会随着必须审查的工件转移。","这些“操作步骤”是操作手册的核心，被分为六个非线性阶段（计划、设计、构建、测试、部署、维护），共同涵盖整个生命周期。","这些步骤是模块化的，组织可以根据其独特需求选择在不同时间优先改造不同阶段。每个操作步骤在“先决条件”下列出其依赖关系，依赖图进一步说明这些关系。","一个阶段通过提交一个工件来结束，而该提交会启动下一个阶段。一个被接受的 intent.md 会触发需求和设计阶段，一个被批准的 spec.md 会触发计划模式，一个合并的 PR 会触发流水线，而生产中违反控制带的情况会写下下一个 intent.md，从而循环继续。","首先，你需要手动提示每一步，最终状态是一个循环，每个被接受的工件都会触发下一个关卡。人的注意力集中在这些关卡上，审查代理标记的内容，而不是从头开始启动每个阶段。","启动软件开发过程的 intent.md 可以通过不同的途径进入。一个人有了想法，会提交工单，或者通过警报发现一个事件（参见阶段 6：维护）。","当一个人有了想法时，他们会与 Claude 头脑风暴，并生成一个 markdown 原型规范。在传统的 SDLC 中，同一个人必须说服产品团队的成员与自己一起撰写该想法，或代表他们来撰写。","Claude 生成的原型规范是人类可读的、受版本控制的，并且可以立即被下一个阶段使用。该原型规范被保存为 intent.md。","无论 intent 是来源于事件触发还是代理生成，其步骤都相同：产品负责人会在提交前审查并修改代理编写的 intent.md。","设置这个流程是平台或工程团队的一次性任务。技术团队成员需要建立 intent home 并决定谁可以向其中写入，因为许多贡献者将来自整个组织。","一旦仓库存在，没有 git 经验的贡献者就不需要直接使用 git。相反，连接到版本控制系统（例如 GitHub）的连接器可以让 Claude 代表他们从 claude.ai 或 Cowork 提交 Markdown 文件。","证据就是提交的 intent.md，它列出了作者、时间戳和完整的修订历史。它记录在 intent home 的 git 历史中。产品负责人批准后，将 intent 送入阶段 2：设计的接受或拒绝决定会被记录为合并或关闭审查。","一旦产品负责人批准，Claude 会根据被接受的 intent.md 制作需求和设计规范。这一过程受组织技能的指导：https://code.claude.com/docs/en/skills，包括品牌、安全、合规和用户体验（UX）。","产品负责人会审查该规范，但不会撰写它。该流程的目标是创建工程团队可依据进行计划的规范，并标记出需要关注的区域。","在几周后的审查中发现问题之前，实时政策会在规范编写过程中被读取和应用。组织技能作为约束应用于规范。规范、生成规范的提示以及生效的技能版本都会被记录在版本控制中。产品负责人签署规范，并将标记的关注事项传达给指定的政策所有者。","工程师在计划模式下启动 Claude Code 会话：https://code.claude.com/docs/en/permission-modes，向 Claude 提供第二阶段设计中的已批准 spec.md，让其进行访谈，并在工程师满意前不断迭代计划。","设计评审在任何代码生成之前进行，此时更改方向仍然只是编辑文档而已。计划模式本身强制执行这一点，因为 Claude 在工程师接受计划前无法编辑文件。计划及其修订记录会与接受者信息一同记录。常规更改由工程师批准，而组织认定的高风险更改则交给技术负责人或架构师处理。","Claude Code 还可以在自动模式下运行，即工程师批准计划后，一旦满意并完成迭代，Claude 可以不依赖每次编辑提示地应用每个更改。随着后续环节的护栏逐步完善（经过调优的 CLAUDE.md、编码政策的技能、阻止不安全操作的钩子，以及 Claude 可以运行的测试套件），自动接受模式成为例行工作的默认模式：紧凑的 spec.md、小范围影响、以及已有测试覆盖的代码。","工作重心现在从用户实时监控代理进行编辑及审核操作，转向更长时间的自主会话后的成果物审查。结合工作树使用时，自动接受模式进一步实现个人和团队的并行操作，并且是实现 SDLC 自主运行及闭环流程（如第六阶段：维护中描述）的基础。","CLAUDE.md：https://code.claude.com/docs/en/memory 为 Claude 提供新加入成员所需的上下文，涵盖规范、命令、架构以及团队最常见的错误。以前存储在人员脑海和维基上的知识，现在变成了一个在每次会话开始时由代理读取的文件，由整个团队维护，并在出现错误时进行迭代。","CLAUDE.md 是版本控制的，因此代理遵循的指令是可审查和可追溯的。团队规范通过该文件应用，对文件的更改记录在 git 历史中，代码所有者在 PR 审查中批准这些更改。","技能是组织使其制度化知识可操作化的方式。这些指令是明确的、版本控制的、广泛应用的，并在政策变更时集中更新。经验法则：为必须一致应用的制度化知识编写技能；不要为属于 CLAUDE.md 或提示的组件编写技能。","技能是一种控制，但属于建议性控制。它使 Claude 在代码编写时更可能遵循政策，但不会强制会话必须遵守。必须始终保持的政策需要技能背后有确定性机制，例如阻止操作的钩子或在 PR 时重新检查政策的审查流程。技能使违规行为罕见，而钩子使其几乎不可能发生。技能调用会记录在会话跟踪中，政策所有者像审查代码一样审查技能更改。","技能是一种建议性控制，而钩子：https://code.claude.com/docs/en/hooks 是其背后的确定性层。Claude 执行的大部分操作是在实现过程中进行文件编辑和 shell 命令，因此构建阶段是钩子最常触发的环节。","支持任何必须无例外遵循其政策的技能。钩子会在匹配其条件的每个操作上运行，因此构建阶段的钩子应快速且限定在发生变更的文件上。较重的检查，例如完整测试套件，应放在提交或 PR 阶段。","要求人工批准的钩子应放在第 5 阶段：部署的关卡中，因为构建阶段的批准提示会让人重新成为所有并行会话的关键路径。","一名工程师可以同时推动多个工作流。","并行会话是另一个完整的 Claude 代码实例，在其自己的 git 工作树中处理一个独立任务：https://code.claude.com/docs/en/worktrees。每个独立的会话彼此之间互不知情，唯一共享的是操作它们的工程师。","子代理：https://code.claude.com/docs/en/sub-agents 在单个会话内运行，作为具有自己上下文窗口和工具限制的作用域助手，适用于在多个任务中重复出现的工作，例如验证应用是否按预期运行。","并行会话增加了工程师可以同时处理的任务数量，而子代理则保持每个会话专注于自身任务。工程师的工作是引导和审查所有会话。","更多的会话意味着更多的输出，因此需要通过仓库中的配置来进行控制。那里设置的钩子和权限适用于所有会话，会话所做的任何操作都会被记录，并归属于运行它的工程师。","始终为 Claude 提供验证自身工作的方式，无论是测试、构建还是截图差异。会话会在工程师看到之前检查自己的工作并修正自己的错误。","反馈循环不应与验证子代理（阶段 3：构建）混淆。反馈循环会贯穿整个任务，运行的次数与工作量相同。另一方面，验证子代理是一种通过在会话认为工作完成后运行一个新上下文窗口来进行最终检查的方式。这样，判定不会因为生成代码时的假设而受到影响。","评估是 AI 原生的阶段门质量保证（stage-gate QA）等价物。在实践中，这意味着每当代理配置更改时都会运行一套测试。每当新的模型被替换或提示被重写时，评估套件会判断代理是否仍然按照同样的标准完成工作。","评估应被视为一个实时套件。随着模型的改进，曾经能够区分情况的测试用例不再有效，需要添加新的测试用例，这些用例基于持续的监控生成。","根据使用场景，某些团队可能更倾向于按固定周期离线运行这些评估，而不是在每次更改时运行。以下步骤适用于持续评估。","评估为 QA 提供了一个与代理输出保持同步的门控。通过合并检查来执行通过率阈值，运行结果会被记录以便随时间比较，并且拥有配置变更的团队会批准它。","Claude 既提供也接受评审。它根据组织的政策审查进来的 PR，并对它自己 PR 的评审意见进行响应。这使得工程师可以专注于在 PR 审查中评估行为，最终归结为判断意图和风险。","职责分离得以保持，因为编写代码的代理无法批准它。REVIEW.md 中的审查政策适用于所有 PR，发现、修复、评级和批准都会记录在 PR 历史中，因此 PR 本身就是审计记录。批准通过人类在分支保护下进行，并依据发现结果作出决策。","构建阶段使用了钩子作为护栏，在无人参与的情况下允许或阻止操作（阶段 3：构建）。钩子还可以提出请求，暂停操作直到特定人员批准，这正是发布门控所需的。","该操作位于阶段 5：部署，因为发布门是最明显的例子，但钩子并非部署特定：它们在 Claude 执行的任何地方都运行。例如，在阶段 3：构建期间，如果没有变更单，钩子可以阻止对迁移和基础设施的编辑；在阶段 4：测试的修复任务中，可阻止代理编辑测试文件。","钩子即审批门控。每次都会对所有人强制执行门控条件。允许和阻止的决定会带时间戳记录。门控还定义了什么算作批准，无论是已批准的变更单还是发布经理的签字。","在 CI/CD 流水线中以非交互方式运行 Claude 代码，对执行进行沙箱隔离以保证长期运行的代理安全，通过 MCP 集成暴露部署，并在代理实际需要前演练回滚路径。","基本原则是代理可以执行到生产门控，但不能通过它。下面的控制措施执行这一原则。","到目前为止，我们讨论了如何将 Claude 添加到 SDLC 流程的每个阶段，每个阶段都需要人类启动初始步骤。然而，本阶段将重点转向 Claude 的自主运行以闭环整个流程。","例如，一个持续运行的监控代理可以在一个错误工单被提出后，创建一个 intent.md，并流转通过需求、计划、构建、测试和审核阶段。第六阶段：维护阶段以无头模式运行，在各阶段之间有独立的可信度门，一个确定性检查或对抗性审核代理，决定前一阶段的输出是继续执行还是升级给人工处理。","一个确定性脚本监控生产环境，并在控制带被突破时调用 Claude。监控违规是循环自主运行模式的一个有益示例，而在阶段末尾提到的 Claude Tag：https://claude.com/product/tag（公开测试版）部分，涵盖了通过不同渠道到达的工作内容。","版本控制的配置实施了等级边界，权限和托管设置拒绝生产访问。调用、发现和分类决策都会记录时间戳。服务负责人对发现进行分类和批准， resulting changes 会经过正常的 PR 审核门，而代理可能触发的运行手册则已事先获得批准。"]},"en":{"title":"AI-Native SDLC Hands-on Guide: How Anthropic Reshapes the Software Development Lifecycle with Claude","summary":"Anthropic has released a practical manual for AI-native SDLC, proposing to reconstruct the traditional six-stage software development lifecycle into a closed-loop process of embedding AI into each stage. The manual points out that when code is no longer a bottleneck, manual processes such as planning, review, and deployment become new constraints. Claude must be used to compress requirements into intent.md, use skill coding standards, replace phased access control with continuous evaluation, and retain manual review of critical code. 🔗 Read the original article via AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"Industry","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"AI-Native SDLC Hands-on Guide: How Anthropic Reshapes the Software Development Lifecycle with Claude - Aioga AI News","description":"Anthropic has released a practical manual for AI-native SDLC, proposing to reconstruct the traditional six-stage software development lifecycle into a closed-loop process of embedd...","url":"https://www.aioga.com/en/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:07.527Z"},"ja":{"title":"AIネイティブSDLCハンズオンガイド:AnthropicがClaudeでソフトウェア開発ライフサイクルをどのように再構築するか","summary":"AnthropicはAIネイティブSDLCの実用マニュアルを発表し、従来の6段階のソフトウェア開発ライフサイクルを各段階にAIを組み込むクローズドループプロセスに再構築することを提案しています。 マニュアルは、コードがもはやボトルネックでなくなったとき、計画、レビュー、デプロイといった手動プロセスが新たな制約となることを指摘しています。Claudeは、要件を intent.md に圧縮し、スキルコーディング標準を使用し、段階的アクセス制御を継続的評価に置き換え、重要なコードの手動レビューを維持するために使わなければなりません。 🔗 原文記事はAIHOTより読むことができます。 https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"業界動向","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"AIネイティブSDLCハンズオンガイド:AnthropicがClaudeでソフトウェア開発ライフサイクルをどのように再構築するか - Aioga AIニュース","description":"AnthropicはAIネイティブSDLCの実用マニュアルを発表し、従来の6段階のソフトウェア開発ライフサイクルを各段階にAIを組み込むクローズドループプロセスに再構築することを提案しています。 マニュアルは、コードがもはやボトルネックでなくなったとき、計画、レビュー、デプロイといった手動プロセスが新たな制約となることを指摘しています。Claudeは、要件を...","url":"https://www.aioga.com/ja/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:07.704Z"},"ko":{"title":"AI 네이티브 SDLC 실습 가이드: Anthropic이 Claude로 소프트웨어 개발 수명 주기를 재구성하는 방법","summary":"Anthropic은 AI 네이티브 SDLC를 위한 실용 매뉴얼을 발표했으며, 전통적인 6단계 소프트웨어 개발 수명주기를 각 단계에 AI를 내장하는 폐쇄 루프 프로세스로 재구성할 것을 제안했습니다. 매뉴얼은 코드가 더 이상 병목 현상이 아니게 되면 계획, 검토, 배포와 같은 수작업 프로세스가 새로운 제약이 된다고 지적합니다. 클로드는 요구사항을 intent.md 압축하고, 스킬 코딩 표준을 사용하며, 단계적 접근 제어를 지속적 평가로 대체하고, 중요한 코드에 대한 수동 검토를 유지하는 데 사용해야 합니다. 🔗 원문 기사는 AIHOT를 통해 읽을 수 있습니다. https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"업계 동향","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"AI 네이티브 SDLC 실습 가이드: Anthropic이 Claude로 소프트웨어 개발 수명 주기를 재구성하는 방법 - Aioga AI 뉴스","description":"Anthropic은 AI 네이티브 SDLC를 위한 실용 매뉴얼을 발표했으며, 전통적인 6단계 소프트웨어 개발 수명주기를 각 단계에 AI를 내장하는 폐쇄 루프 프로세스로 재구성할 것을 제안했습니다. 매뉴얼은 코드가 더 이상 병목 현상이 아니게 되면 계획, 검토, 배포와 같은 수작업 프로세스가 새로운 제약이 된다고 지적합니다...","url":"https://www.aioga.com/ko/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:16.445Z"},"es":{"title":"Guía práctica de SDLC nativa con IA: Cómo Anthropic transforma el ciclo de vida del desarrollo de software con Claude","summary":"Anthropic ha publicado un manual práctico para SDLC nativo de IA, proponiendo reconstruir el ciclo de vida tradicional de seis etapas del desarrollo de software en un proceso cerrado de integración de IA en cada etapa. El manual señala que cuando el código deja de ser un cuello de botella, los procesos manuales como la planificación, revisión y despliegue se convierten en nuevas restricciones. Claude debe usarse para comprimir los requisitos en intent.md, emplear estándares de codificación por habilidades, reemplazar el control de acceso por fases por una evaluación continua y conservar la revisión manual del código crítico. 🔗 Lee el artículo original a través de AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"Industria","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"Guía práctica de SDLC nativa con IA: Cómo Anthropic transforma el ciclo de vida del desarrollo de software con Claude - Aioga Noticias de IA","description":"Anthropic ha publicado un manual práctico para SDLC nativo de IA, proponiendo reconstruir el ciclo de vida tradicional de seis etapas del desarrollo de software en un proceso cerra...","url":"https://www.aioga.com/es/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:16.469Z"},"fr":{"title":"Guide pratique SDLC natif de l’IA : Comment Anthropic remodele le cycle de vie du développement logiciel avec Claude","summary":"Anthropic a publié un manuel pratique pour les SDLC natifs-IA, proposant de reconstruire le cycle de vie traditionnel en six étapes de développement logiciel en un processus en boucle fermée d’intégration de l’IA dans chaque étape. Le manuel souligne que lorsque le code n’est plus un goulot d’étranglement, les processus manuels tels que la planification, la révision et le déploiement deviennent de nouvelles contraintes. Claude doit être utilisé pour compresser les exigences en intent.md, utiliser des standards de codage par compétences, remplacer le contrôle d’accès phasé par une évaluation continue et conserver la révision manuelle du code critique. 🔗 Lisez l’article original via AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"Industrie","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"Guide pratique SDLC natif de l’IA : Comment Anthropic remodele le cycle de vie du développement logiciel avec Claude - Aioga Actualités IA","description":"Anthropic a publié un manuel pratique pour les SDLC natifs-IA, proposant de reconstruire le cycle de vie traditionnel en six étapes de développement logiciel en un processus en bou...","url":"https://www.aioga.com/fr/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:25.053Z"},"de":{"title":"KI-native SDLC Hands-on-Leitfaden: Wie anthropologisch den Softwareentwicklungszyklus mit Claude neu gestaltet","summary":"Anthropic hat ein praktisches Handbuch für KI-natives SDLC veröffentlicht und vorschlägt, den traditionellen sechsstufigen Softwareentwicklungszyklus in einen geschlossenen Prozess umzuwandeln, bei dem KI in jede Stufe eingebettet wird. Das Handbuch weist darauf hin, dass, wenn Code kein Engpass mehr ist, manuelle Prozesse wie Planung, Überprüfung und Bereitstellung zu neuen Einschränkungen werden. Claude muss verwendet werden, um Anforderungen in intent.md zu komprimieren, Skill-Codierungsstandards zu verwenden, phasenweise Zugriffskontrolle durch kontinuierliche Evaluierung zu ersetzen und die manuelle Überprüfung kritischen Codes beizubehalten. 🔗 Lesen Sie den Originalartikel über AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"KI-native SDLC Hands-on-Leitfaden: Wie anthropologisch den Softwareentwicklungszyklus mit Claude neu gestaltet - Aioga KI-News","description":"Anthropic hat ein praktisches Handbuch für KI-natives SDLC veröffentlicht und vorschlägt, den traditionellen sechsstufigen Softwareentwicklungszyklus in einen geschlossenen Prozess...","url":"https://www.aioga.com/de/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:25.121Z"},"pt-BR":{"title":"Guia Prático SDLC Nativo de IA: Como a Antropia Remodela o Ciclo de Vida do Desenvolvimento de Software com Claude","summary":"A Anthropic lançou um manual prático para o SDLC nativo de IA, propondo reconstruir o ciclo de vida tradicional de seis estágios de desenvolvimento de software em um processo de ciclo fechado de incorporação de IA em cada estágio. O manual destaca que, quando o código não é mais um gargalo, processos manuais como planejamento, revisão e implantação tornam-se novas restrições. Claude deve ser usado para comprimir requisitos em intent.md, usar padrões de codificação de habilidades, substituir o controle de acesso faseado por avaliação contínua e manter a revisão manual do código crítico. 🔗 Leia o artigo original via AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"Guia Prático SDLC Nativo de IA: Como a Antropia Remodela o Ciclo de Vida do Desenvolvimento de Software com Claude - Aioga Notícias de IA","description":"A Anthropic lançou um manual prático para o SDLC nativo de IA, propondo reconstruir o ciclo de vida tradicional de seis estágios de desenvolvimento de software em um processo de ci...","url":"https://www.aioga.com/pt-BR/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:33.820Z"},"ru":{"title":"Практическое руководство по SDLC на основе искусственного интеллекта: как Anthropic меняет жизненный цикл разработки программного обеспечения с Клод","summary":"Anthropic выпустила практическое руководство по SDLC, основанному на основе искусственного интеллекта, предлагая реконструировать традиционный шестиступенчатый жизненный цикл разработки программного обеспечения в замкнутый цикл внедрения ИИ в каждый этап. В руководстве отмечается, что когда код перестаёт быть узким местом, ручные процессы, такие как планирование, обзор и развертывание, становятся новыми ограничениями. Claude необходимо использовать для сжатия требований в intent.md, использования стандартов кодирования навыков, замены поэтапного контроля доступа на непрерывную оценку и сохранения ручного пересмотра критически важного кода. 🔗 Прочитайте оригинальную статью на сайте AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"Практическое руководство по SDLC на основе искусственного интеллекта: как Anthropic меняет жизненный цикл разработки программного обеспечения с Клод - Aioga Новости ИИ","description":"Anthropic выпустила практическое руководство по SDLC, основанному на основе искусственного интеллекта, предлагая реконструировать традиционный шестиступенчатый жизненный цикл разра...","url":"https://www.aioga.com/ru/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:33.794Z"},"ar":{"title":"دليل عملي لتطوير البرمجيات المبدعة بالذكاء الاصطناعي: كيف يعيد Anthropic تشكيل دورة حياة تطوير البرمجيات مع كلود","summary":"أصدرت Anthropic دليلا عمليا لتطوير البرمجيات المبني على الذكاء الاصطناعي، يقترح إعادة بناء دورة تطوير البرمجيات التقليدية ذات الست مراحل إلى عملية مغلقة لدمج الذكاء الاصطناعي في كل مرحلة. يشير الدليل إلى أنه عندما لا يعد الكود عنق زجاجة، تصبح العمليات اليدوية مثل التخطيط والمراجعة والنشر قيودا جديدة. يجب استخدام Claude لضغط المتطلبات إلى intent.md، واستخدام معايير ترميز المهارات، واستبدال التحكم المرحلي في الوصول بالتقييم المستمر، والاحتفاظ بالمراجعة اليدوية للكود الحيوي. 🔗 اقرأ المقال الأصلي عبر AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"دليل عملي لتطوير البرمجيات المبدعة بالذكاء الاصطناعي: كيف يعيد Anthropic تشكيل دورة حياة تطوير البرمجيات مع كلود - Aioga أخبار الذكاء الاصطناعي","description":"أصدرت Anthropic دليلا عمليا لتطوير البرمجيات المبني على الذكاء الاصطناعي، يقترح إعادة بناء دورة تطوير البرمجيات التقليدية ذات الست مراحل إلى عملية مغلقة لدمج الذكاء الاصطناعي في كل...","url":"https://www.aioga.com/ar/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:42.557Z"},"hi":{"title":"एआई-नेटिव एसडीएलसी हैंड्स-ऑन गाइड: कैसे एंथ्रोपिक क्लाउड के साथ सॉफ्टवेयर विकास जीवनचक्र को नया आकार देता है","summary":"एंथ्रोपिक ने एआई-नेटिव एसडीएलसी के लिए एक व्यावहारिक मैनुअल जारी किया है, जिसमें पारंपरिक छह-चरण सॉफ्टवेयर विकास जीवनचक्र को प्रत्येक चरण में एआई को एम्बेड करने की एक बंद-लूप प्रक्रिया में पुनर्निर्माण करने का प्रस्ताव है। मैनुअल बताता है कि जब कोड अब एक अड़चन नहीं है, तो योजना, समीक्षा और तैनाती जैसी मैन्युअल प्रक्रियाएं नई बाधाएं बन जाती हैं। क्लाउड का उपयोग आवश्यकताओं को intent.md में संपीड़ित करने, कौशल कोडिंग मानकों का उपयोग करने, चरणबद्ध अभिगम नियंत्रण को निरंतर मूल्यांकन के साथ बदलने और महत्वपूर्ण कोड की मैन्युअल समीक्षा बनाए रखने के लिए किया जाना चाहिए। 🔗 AIHOT के माध्यम से मूल लेख पढ़ें · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"एआई-नेटिव एसडीएलसी हैंड्स-ऑन गाइड: कैसे एंथ्रोपिक क्लाउड के साथ सॉफ्टवेयर विकास जीवनचक्र को नया आकार देता है - Aioga AI समाचार","description":"एंथ्रोपिक ने एआई-नेटिव एसडीएलसी के लिए एक व्यावहारिक मैनुअल जारी किया है, जिसमें पारंपरिक छह-चरण सॉफ्टवेयर विकास जीवनचक्र को प्रत्येक चरण में एआई को एम्बेड करने की एक बंद-लूप प्रक्...","url":"https://www.aioga.com/hi/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:42.487Z"},"it":{"title":"Guida pratica SDLC nativa AI: Come Anthropic rimodella il ciclo di vita dello sviluppo software con Claude","summary":"Anthropic ha pubblicato un manuale pratico per l'SDLC nativo dell'IA, proponendo di ricostruire il tradizionale ciclo di sviluppo software in sei fasi in un processo a ciclo chiuso di incorporazione dell'IA in ogni fase. Il manuale sottolinea che quando il codice non è più un collo di bottiglia, i processi manuali come pianificazione, revisione e distribuzione diventano nuovi vincoli. Claude deve essere usato per comprimere i requisiti in intent.md, utilizzare standard di codifica per competenze, sostituire il controllo di accesso a fasi con una valutazione continua e mantenere la revisione manuale del codice critico. 🔗 Leggi l'articolo originale su AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"Guida pratica SDLC nativa AI: Come Anthropic rimodella il ciclo di vita dello sviluppo software con Claude - Aioga Notizie IA","description":"Anthropic ha pubblicato un manuale pratico per l'SDLC nativo dell'IA, proponendo di ricostruire il tradizionale ciclo di sviluppo software in sei fasi in un processo a ciclo chiuso...","url":"https://www.aioga.com/it/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:51.007Z"},"nl":{"title":"AI-native SDLC Hands-on Gids: Hoe Antropopisch de softwareontwikkelingslevenscyclus hervormt met Claude","summary":"Anthropic heeft een praktische handleiding uitgebracht voor AI-native SDLC, waarin wordt voorgesteld om de traditionele zesfasige softwareontwikkelingslevenscyclus te reconstrueren tot een gesloten loopproces waarbij AI in elke fase wordt ingebed. De handleiding wijst erop dat wanneer code geen bottleneck meer is, handmatige processen zoals planning, review en deployment nieuwe beperkingen worden. Claude moet worden gebruikt om eisen samen te brengen tot intent.md, vaardigheidscoderingsstandaarden te gebruiken, gefaseerde toegangscontrole te vervangen door continue evaluatie en handmatige beoordeling van kritieke code te behouden. 🔗 Lees het originele artikel via AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"AI-native SDLC Hands-on Gids: Hoe Antropopisch de softwareontwikkelingslevenscyclus hervormt met Claude - Aioga AI-nieuws","description":"Anthropic heeft een praktische handleiding uitgebracht voor AI-native SDLC, waarin wordt voorgesteld om de traditionele zesfasige softwareontwikkelingslevenscyclus te reconstrueren...","url":"https://www.aioga.com/nl/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:51.250Z"},"tr":{"title":"Yapay Zeka Doğumlu SDLC Uygulamalı Rehber: Anthropic, Claude ile Yazılım Geliştirme Yaşam Döngüsünü Nasıl Yeniden Şekillendiriyor","summary":"Anthropic, yapay zeka tabanlı SDLC için pratik bir el kitabı yayımladı ve geleneksel altı aşamalı yazılım geliştirme yaşam döngüsünü her aşamaya yapay zeka entegre eden kapalı döngü sürecine dönüştürmeyi öneriyor. Kılavuz, kod artık bir darboğaz olmadığında planlama, inceleme ve dağıtım gibi manuel süreçlerin yeni kısıtlamalar haline geldiğini vurguluyor. Claude, gereksinimleri intent.md içine sıkıştırmak, beceri kodlama standartlarını kullanmak, aşamalı erişim kontrolünü sürekli değerlendirmeyle değiştirmek ve kritik kodun manuel incelemesini sürdürmek için kullanılmalıdır. 🔗 Orijinal makaleyi AIHOT üzerinden okuyun · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"Yapay Zeka Doğumlu SDLC Uygulamalı Rehber: Anthropic, Claude ile Yazılım Geliştirme Yaşam Döngüsünü Nasıl Yeniden Şekillendiriyor - Aioga AI Haberleri","description":"Anthropic, yapay zeka tabanlı SDLC için pratik bir el kitabı yayımladı ve geleneksel altı aşamalı yazılım geliştirme yaşam döngüsünü her aşamaya yapay zeka entegre eden kapalı döng...","url":"https://www.aioga.com/tr/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:42:59.327Z"},"vi":{"title":"Hướng dẫn thực hành về SDLC bản địa AI: Cách Anthropic định hình lại vòng đời phát triển phần mềm cùng Claude","summary":"Anthropic đã phát hành một hướng dẫn thực tiễn cho SDLC gốc AI, đề xuất tái cấu trúc vòng đời phát triển phần mềm truyền thống gồm sáu giai đoạn thành một quy trình khép kín nhúng AI vào mỗi giai đoạn. Sổ tay chỉ ra rằng khi mã nguồn không còn là nút thắt cổ chai, các quy trình thủ công như lập kế hoạch, xem xét và triển khai trở thành những ràng buộc mới. Claude phải được sử dụng để nén yêu cầu vào intent.md, sử dụng tiêu chuẩn mã hóa kỹ năng, thay thế kiểm soát truy cập theo giai đoạn bằng đánh giá liên tục, và duy trì việc xem xét thủ công các mã quan trọng. 🔗 Đọc bài viết gốc qua AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"Hướng dẫn thực hành về SDLC bản địa AI: Cách Anthropic định hình lại vòng đời phát triển phần mềm cùng Claude - Tin tức AI Aioga","description":"Anthropic đã phát hành một hướng dẫn thực tiễn cho SDLC gốc AI, đề xuất tái cấu trúc vòng đời phát triển phần mềm truyền thống gồm sáu giai đoạn thành một quy trình khép kín nhúng...","url":"https://www.aioga.com/vi/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:43:00.040Z"},"id":{"title":"Panduan Praktik SDLC AI-Native: Bagaimana Anthropic Membentuk Ulang Siklus Hidup Pengembangan Perangkat Lunak bersama Claude","summary":"Anthropic telah merilis manual praktis untuk SDLC AI-native, yang mengusulkan untuk merekonstruksi siklus hidup pengembangan perangkat lunak tradisional enam tahap menjadi proses tertutup untuk menyisipkan AI ke dalam setiap tahap. Manual tersebut menunjukkan bahwa ketika kode tidak lagi menjadi hambatan, proses manual seperti perencanaan, tinjauan, dan penerapan menjadi kendala baru. Claude harus digunakan untuk mengompres persyaratan menjadi intent.md, menggunakan standar pengkode keterampilan, mengganti kontrol akses bertahap dengan evaluasi berkelanjutan, dan mempertahankan tinjauan manual kode kritis. 🔗 Baca artikel asli melalui AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"Panduan Praktik SDLC AI-Native: Bagaimana Anthropic Membentuk Ulang Siklus Hidup Pengembangan Perangkat Lunak bersama Claude - Berita AI Aioga","description":"Anthropic telah merilis manual praktis untuk SDLC AI-native, yang mengusulkan untuk merekonstruksi siklus hidup pengembangan perangkat lunak tradisional enam tahap menjadi proses t...","url":"https://www.aioga.com/id/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:43:07.904Z"},"th":{"title":"คู่มือ SDLC แบบ AI-Native แบบลงมือทํา: วิธีที่ Anthropic ปรับเปลี่ยนวงจรชีวิตการพัฒนาซอฟต์แวร์กับ Claude","summary":"Anthropic ได้เผยแพร่คู่มือปฏิบัติสําหรับ SDLC ที่พัฒนาโดย AI โดยเสนอให้สร้างวงจรชีวิตการพัฒนาซอฟต์แวร์แบบหกขั้นตอนแบบดั้งเดิมให้เป็นกระบวนการปิดที่ฝัง AI ลงในแต่ละขั้นตอน คู่มือชี้ให้เห็นว่าเมื่อโค้ดไม่ใช่คอขวดอีกต่อไป กระบวนการที่ทําด้วยมือ เช่น การวางแผน การตรวจสอบ และการนําไปใช้ จะกลายเป็นข้อจํากัดใหม่ Claude ต้องถูกใช้เพื่อบีบอัดข้อกําหนดให้เป็น intent.md ใช้มาตรฐานการเขียนโค้ดทักษะ แทนที่การควบคุมการเข้าถึงแบบเป็นขั้นตอนด้วยการประเมินผลอย่างต่อเนื่อง และรักษาการตรวจสอบโค้ดสําคัญด้วยมือ 🔗 อ่านบทความต้นฉบับผ่าน AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"คู่มือ SDLC แบบ AI-Native แบบลงมือทํา: วิธีที่ Anthropic ปรับเปลี่ยนวงจรชีวิตการพัฒนาซอฟต์แวร์กับ Claude - ข่าว AI Aioga","description":"Anthropic ได้เผยแพร่คู่มือปฏิบัติสําหรับ SDLC ที่พัฒนาโดย AI โดยเสนอให้สร้างวงจรชีวิตการพัฒนาซอฟต์แวร์แบบหกขั้นตอนแบบดั้งเดิมให้เป็นกระบวนการปิดที่ฝัง AI ลงในแต่ละขั้นตอน คู่มือชี้...","url":"https://www.aioga.com/th/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:43:07.871Z"},"pl":{"title":"AI-Native SDLC Praktyczny Przewodnik: Jak Anthropic przekształca cykl życia tworzenia oprogramowania z Claude'em","summary":"Anthropic opublikował praktyczny podręcznik dla natywnego SDLC dla AI, proponując przebudowę tradycyjnego, sześcioetapowego cyklu rozwoju oprogramowania w zamknięty proces osadzania AI w każdym etapie. Instrukcja wskazuje, że gdy kod przestaje być wąskim gardłem, procesy ręczne, takie jak planowanie, przegląd i wdrażanie, stają się nowymi ograniczeniami. Claude musi być używany do skompresowania wymagań do intent.md, stosowania standardów kodowania umiejętności, zastąpienia fazowej kontroli dostępu ciągłą ewaluacją oraz zachowania ręcznej kontroli krytycznego kodu. 🔗 Przeczytaj oryginalny artykuł za pośrednictwem AIHOT · https://aihot.virxact.com/items/cmt31oi0x0ehyro6tui3xycqe","category":"行业动态","source":"Claude：Blog（网页","aggregationSource":"Claude：Blog（网页","pageTitle":"AI-Native SDLC Praktyczny Przewodnik: Jak Anthropic przekształca cykl życia tworzenia oprogramowania z Claude'em - Aioga Wiadomości AI","description":"Anthropic opublikował praktyczny podręcznik dla natywnego SDLC dla AI, proponując przebudowę tradycyjnego, sześcioetapowego cyklu rozwoju oprogramowania w zamknięty proces osadzani...","url":"https://www.aioga.com/pl/news/cmt31oi0x0ehyro6tui3xycqe/","contentTranslated":true,"sourceHash":"21e324b8a95d3c7e","translatedAt":"2026-08-21T14:43:16.527Z"}},"evidenceTier":"verified-news","reviewStatus":"editorial-selected","indexable":true,"editorialCover":""}}