> For the complete documentation index, see [llms.txt](https://docs.cherryai.com.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cherryai.com.cn/docs/zhong-wen-fan-ti/advanced-basic/cases/project-delivery.md).
# Agent 項目文件交付
營運同事要將一批零散資料整理成索引、摘要同交付文件。為咗避免誤改原件，需要提早講清楚 Agent 嘅工作目錄、可修改範圍同驗收方式。
## 適合嘅任務
* 將零散資料整理成目錄同索引；
* 根據模板生成多份文件；
* 修改程式碼並留下變更說明；
* 批量改名、轉換或者檢查文件。
Agent 工作區會將任務、模型、工作目錄同交付文件放喺同一頁面。
長任務先睇【狀態】面板係咪正在執行、等待批准或者已經完成。
交付物生成之後要真係打開檢查。圖中網頁預覽已經顯示標題、檢查項同建議，唔係空白占位。
## 操作流程
{% stepper %}
{% step %}
### 1. 選擇最小工作目錄
淨係揀而家個項目目錄。重要文件先有備份或者版本記錄，權限由【逐次確認】開始。
{% endstep %}
{% step %}
### 2. 明確可改同不可改範圍
寫清楚邊啲文件只可以讀取、產物放喺邊度、邊啲操作一定要先確認，同埋完成標準。
{% endstep %}
{% step %}
### 3. 先畀 Agent 列計劃
高風險任務可以用【僅規劃】。確認文件清單同步驟之後，再切換到允許編輯嘅模式執行。
{% endstep %}
{% step %}
### 4. 喺右側檢查狀態同文件
長任務先睇【狀態】係咪等待批准；產物生成後喺【文件】入面預覽。確認無誤再交接，唔好用「任務結束」代替驗收。
{% endstep %}
{% endstepper %}
## 示例任務
```
整理而家個目錄。raw/ 入面嘅文件係只讀；喺 deliverables/ 底下建立索引、摘要同缺失資料清單。任何刪除、覆蓋或者批量改名都要先攞確認。最後列出新增同修改咗嘅文件。
```
## 推薦組合
| 能力 | 建議用法 | 點解 |
| ---- | ------------ | ------------------- |
| 工作目錄 | 每個項目用獨立目錄 | 文件邊界同交付位置清楚 |
| 權限 | 修改文件保持【逐次確認】 | 方便發現誤刪、覆蓋同越界寫入 |
| 狀態面板 | 結束前檢查產物同失敗步驟 | 唔好淨係以「Agent 話完成咗」為準 |
| 新任務 | 新階段或者新客戶另開任務 | 避免歷史要求影響而家嘅交付 |
{% hint style="danger" %}
【完全訪問】會減少確認，但亦都會擴大誤操作影響。只有喺隔離、可信同可恢復嘅目錄入面，先考慮暫時使用。
{% endhint %}
---
# 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://docs.cherryai.com.cn/docs/zhong-wen-fan-ti/advanced-basic/cases/project-delivery.md?ask=&goal=
```
`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.
