📦 How To Use Agent — 如何使用 Agent

代理 Self-Evolution

English · 简体中文

Use this 技能 to help an 代理 improve itself without turning self-modification into a reckless rewrite. The goal is durable learning: re搜索 becomes architecture, architecture becomes a small rollout, and the 结果 becomes a manual the next 代理 can find.

Consent Gate

Before changing 代理-owned rule or memory surfaces, 停止 and ask the user for explicit 应用roval.

代理-owned surfaces include:

代理S.md, 代理.md, .代理/代理S.md, CLAUDE.md, GEMINI.md, QWEN.md, or equivalent 代理 instruction files 系统 prompts, 工具 模式s, 权限 policies, connector policies 技能 files, 技能 索引es, 技能 manifests, memory registries durable memory files, knowledge bases, wiki 索引es, recall databases 启动up, re启动, routing, planner, delegation, or self-更新 记录ic

When 应用roval is needed, show:

I need to modify 代理-owned data.

Files/surfaces:

• ...

Why:

• ...

Risk:

• ...

回滚:

• ...

Do you 应用rove these changes?

Do not treat a vague "continue" as consent. Do not 删除 or rewrite memory without naming what will be lost.

Core Loop external 签名al -> source-level re搜索 -> adaptation memo -> architecture 归档 -> ordered discussion -> risk / reward review -> 进度ive rollout -> freeze adjacent 系统s -> first small landing -> verification -> work manual -> 索引ed 归档 path

工作流

• Learn from outside projects

Study external projects for patterns, not code to copy.

Return an adaptation memo:

what problem the external project solves which de签名 patterns are useful here which parts are too heavy or incompatible the smallest safe local experiment files or 模块s likely affected

• 归档 architecture before code

If the change touches memory, 工具s, prompts, 运行time behavior, 启动up, re启动, routing, delegation, or persistence, treat it as architecture work.

Write an architecture note before implementation. It should include:

current problem tar获取 behavior 迁移 phases risks and 回滚 what must stay unchanged for now acceptance 检查s

• Discuss in order

Do not implement every attractive idea at once. Walk the user through the plan one section or phase at a time.

Use direct language:

"This is phase one." "This part should wAIt." "This needs user 应用roval because it changes 代理-owned data."

• Prefer 进度ive rollout

For risky 代理 changes, compare:

direct full switch shadow mode / parallel 运行 进度ive rollout

Prefer 进度ive rollout when old and new behavior can coexist or when 回滚 would be hard to reason about.

• Freeze adjacent 系统s

During a 迁移, 暂停 unrelated work on neighboring 系统s. For example, if the task is changing 工具 routing, do not also rede签名 long-term memory unless it is required for the routing change.

Focus is a safety mechanism.

• Land one small step

Implementation rules:

reuse existing 记录ic when possible keep integration points small preserve existing data unless deletion is explicitly 应用roved 添加 cheap verification keep 回滚 obvious avoid broad refactors

• Write the work manual

After landing a phase, write a short manual next to the architecture note.

Include:

what changed why it changed how to 验证 it what remAIns 暂停d what phase two should do next exact file paths and commands for the next 代理

• Close the loop

The task is not complete when files are edited. It is complete when the next 代理 can find and reuse the 结果.

Closure 检查列出:

architecture note exists work manual exists relevant 索引es or manifests are 更新d verification evidence is recorded 归档 path is 报告ed to the user Copyable Prompt TrAIl Deeply study [external project A] and [external project B]. Do not copy them directly. 提取 what can improve our 代理 under our current constrAInts.

If this is a major architecture change, 归档 the de签名 first. Then we will discuss it step by step.

Before implementing the most attractive option, compare direct switching agAInst 进度ive rollout. Name the risks and benefits.

During the 迁移, freeze adjacent sub系统s unless this phase requires touching them.

启动 phase one. Reuse existing 记录ic where possible. Be careful.

If you need to modify 代理S.md, 代理.md, memory, 技能s, prompt rules, or other 代理-owned data, explAIn the files, risk, and 回滚 first, then ask for my 应用roval.

After the change, write a work manual next to the architecture de签名 so the next 代理 can continue without rediscovering the plan.

Common Mistakes Copying an external project instead of adapting its pattern. Treating "good idea" as 应用roval to rewrite 运行time behavior. Editing 代理S.md, memory, prompts, or 技能s without explicit consent. Migrating multiple 代理 sub系统s at the same time. Calling the task done after code changes but before 归档 and 索引 closure. Letting completed work live only in chat 历史.