https://www.chunshuijiancha.top/categories/llm/Recent content in LLM应用 on 春水煎茶Hugozh-cnThu, 04 Jun 2026 23:00:00 +0800https://www.chunshuijiancha.top/posts/llm/agent/base-agent-reins/Thu, 04 Jun 2026 23:00:00 +0800https://www.chunshuijiancha.top/posts/llm/agent/base-agent-reins/很多人以为构建 Agent 系统，最难的问题是&quot;让 LLM 更聪明&quot;。真正进入生产环境，你会发现把你逼疯的不是模型效果，而是模型的“不确定性”。https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-1-onboarding/Thu, 16 Apr 2026 10:00:00 +0800https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-1-onboarding/通过 SDD + OpenSpec，我们在一个真实的存量项目中，用 AI 生成了 9600+ 行可编译、可测试的代码，手动修改不到 50 行。本文记录了完整的实践过程、评测结果和踩坑经验。https://www.chunshuijiancha.top/posts/llm/agent/production-grade-skill/Mon, 01 Jun 2026 23:00:00 +0800https://www.chunshuijiancha.top/posts/llm/agent/production-grade-skill/写个Skill 一天就能上线，但生产级的Skill你会发现远没有那么简单。Skill 设计不是 prompt 工程，而是一门系统工程https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-2-architecture/Sun, 19 Apr 2026 20:00:00 +0800https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-2-architecture/<h2 id="openspec-架构">OpenSpec 架构</h2> <h3 id="整体架构">整体架构</h3> <p>可以把它理解成三层：</p> <ul> <li><strong>状态层</strong>：仓库目录本身就是状态存储</li> <li><strong>计算层</strong>：schema + dependency graph + validator</li> <li><strong>交互层</strong>：CLI 和 skills，把结构化状态喂给 AI 或人</li> </ul> <p>这套分层很重要，因为它避免了一个常见问题：把“流程”硬编码进 prompt。在 OpenSpec 里，prompt 只是表现层；真正的工作流定义在 schema 中，真正的状态在文件系统里。</p> <p><img alt="OpenSpec 整体架构图（Excalidraw 重绘）" loading="lazy" src="https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-2-architecture/arch_overall_excalidraw.svg"></p> <h3 id="核心对象">核心对象</h3> <p>OpenSpec 其实有4个核心对象：</p> <ul> <li><strong><code>specs</code></strong>：当前系统行为的 source of truth</li> <li><strong><code>changes</code></strong>：待合入的变更包</li> <li><strong><code>schema</code></strong>：工作流定义，决定有哪些 artifact、它们如何依赖</li> <li><strong><code>archive</code></strong>：变更完成后的历史沉淀</li> </ul> <p>如果第一次使用，你可能会好奇schema是什么?</p> <p><img alt="img.png" loading="lazy" src="https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-2-architecture/arch_01.webp"></p> <p>在每次变更文件夹中，<code>.openspec.yaml</code>文件中就有 <code>schema</code>字段，默认值为<code>spec-driven</code>。可以在源码中，看到<code>spec-driven</code>定义了产出物（artifacts）的目录、文件名、文件格式、生成Prompt等，以及实施阶段（apply）读取的任务文件和Prompt。 这是OpenSpec预定义的schema，我们也可以自定义schema，对他进行扩展。</p> <p><img alt="img.png" loading="lazy" src="https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-2-architecture/arch_schema_01.webp"></p> <p><img alt="img.png" loading="lazy" src="https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-2-architecture/arch_schema_02.webp"></p> <h3 id="工作流">工作流</h3> <p>如下是OpenSpec默认的工作流，通过schema定义中的<code>requires</code>字段定义依赖关系。</p> <div class="mermaid-container"> <div class="mermaid"> flowchart LR proposal --&gt; specs proposal --&gt; design specs --&gt; tasks design --&gt; tasks tasks --&gt; apply apply --&gt; archive </div> </div><div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#f92672">artifacts</span>: </span></span><span style="display:flex;"><span> - <span style="color:#f92672">id</span>: <span style="color:#ae81ff">proposal</span> </span></span><span style="display:flex;"><span> <span style="color:#f92672">generates</span>: <span style="color:#ae81ff">proposal.md</span> </span></span><span style="display:flex;"><span> <span style="color:#f92672">requires</span>: [] </span></span><span style="display:flex;"><span> </span></span><span style="display:flex;"><span> - <span style="color:#f92672">id</span>: <span style="color:#ae81ff">specs</span> </span></span><span style="display:flex;"><span> <span style="color:#f92672">generates</span>: <span style="color:#ae81ff">specs/**/*.md</span> </span></span><span style="display:flex;"><span> <span style="color:#f92672">requires</span>: [<span style="color:#ae81ff">proposal]</span> </span></span><span style="display:flex;"><span> </span></span><span style="display:flex;"><span> - <span style="color:#f92672">id</span>: <span style="color:#ae81ff">design</span> </span></span><span style="display:flex;"><span> <span style="color:#f92672">generates</span>: <span style="color:#ae81ff">design.md</span> </span></span><span style="display:flex;"><span> <span style="color:#f92672">requires</span>: [<span style="color:#ae81ff">proposal]</span> </span></span><span style="display:flex;"><span> </span></span><span style="display:flex;"><span> - <span style="color:#f92672">id</span>: <span style="color:#ae81ff">tasks</span> </span></span><span style="display:flex;"><span> <span style="color:#f92672">generates</span>: <span style="color:#ae81ff">tasks.md</span> </span></span><span style="display:flex;"><span> <span style="color:#f92672">requires</span>: [<span style="color:#ae81ff">specs, design]</span> </span></span><span style="display:flex;"><span><span style="color:#f92672">apply</span>: </span></span><span style="display:flex;"><span> <span style="color:#f92672">requires</span>: [<span style="color:#ae81ff">tasks]</span> </span></span></code></pre></div><ol> <li>这里的设计哲学：<strong>dependency is an enabler, not a gate</strong>。</li> </ol> <p>也就是说，依赖表示“现在什么是可做的”，而不是“你必须严格按唯一顺序前进”。这和很多传统 spec 流程差异很大：后者把流程建模成 phase，前者把流程建模成 action + dependency。</p>https://www.chunshuijiancha.top/posts/llm/devops/relation-stability/Sun, 17 May 2026 17:00:00 +0800https://www.chunshuijiancha.top/posts/llm/devops/relation-stability/作为一名架构师，我经常被问到一个问题：&ldquo;你的系统是怎么做到连续两年没有出过 P0/P1 级故障的？&quot;。我们确实做了很多事情，但是一直没有进行系统的梳理，想趁此机会把思考、尝试讲出来。https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-3-enhancements/Thu, 16 Apr 2026 10:00:00 +0800https://www.chunshuijiancha.top/posts/llm/xdd/openspec/part-3-enhancements/<p>ing&hellip;</p>