> For the complete documentation index, see [llms.txt](https://zhouhao4221.gitbook.io/haiqing-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zhouhao4221.gitbook.io/haiqing-docs/05-workflow.md).

# 05 · 工作流程

标准化工程流程。在 AI 驱动团队中，工作如何从想法流转到交付。

***

## 目的

AI 输出不稳定，很多时候不是模型的问题，而是流程没有结构。本章节解释如何设计让 AI 稳定参与的工程流程——明确每个阶段 AI 做什么、人做什么、交接点在哪里。

***

## 本章节文档

| 文档                                                                         | 内容                                        |
| -------------------------------------------------------------------------- | ----------------------------------------- |
| [dev-cycle.md](/haiqing-docs/05-workflow/dev-cycle.md)                     | 从需求到 PR 合并的日常开发循环，含结构化需求模板和 Sprint AI 检查点 |
| [spec-code-alignment.md](/haiqing-docs/05-workflow/spec-code-alignment.md) | 规格与代码如何对齐，以及如何防止文档和代码随时间漂移                |
| [incident-response.md](/haiqing-docs/05-workflow/incident-response.md)     | 生产事故响应流程，AI 辅助根因分析与修复的操作步骤                |
| [release-workflow.md](/haiqing-docs/05-workflow/release-workflow.md)       | 发布工作流，从代码冻结到交付后监控，AI 分工与人工职责边界            |
| [knowledge-transfer.md](/haiqing-docs/05-workflow/knowledge-transfer.md)   | 知识外化实践：三个层次让项目可以被任何人接手，不依赖老人带             |

***

## 一条核心规则

非结构化输入只能在第 1 步进入工作流程。到设计阶段时，一切都必须已结构化。后续阶段发现的模糊，根因通常是需求结构化不彻底，而不是 AI 能力不足。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://zhouhao4221.gitbook.io/haiqing-docs/05-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.