taodeng/memory-continuity
1
0
Fork 0
mirror of https://github.com/dtzp555-max/memory-continuity.git synced 2026-07-21 21:15:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

memory: prefer delegating implementation to codex_worker

Browse Source
This commit is contained in:
taodeng
2026-03-07 20:35:57 +10:00
parent 1fbaea680b
commit fe0adfba35
2 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
MEMORY.md
+2
View File
@@ -18,6 +18,8 @@
- **main** acts as **PM/architect/reviewer**: requirements, task breakdown, prioritization, risk calls, progress updates, and final summaries to Tao.
- Execution agents should be **role-specialized** and do the implementation work.
- **codex_worker** is the dedicated Codex execution agent for coding tasks.
- Default delegation rule: unless a task is truly tiny and can be finished in one short pass, **main should not default to personally coding/editing files**; implementation work should be delegated to **codex_worker** first.
- Good candidates for main to do directly: tiny edits, very small linear fixes, or short actions that are not worth execution-agent handoff.
- For complex projects, create more specialized agents as needed (e.g. frontend/backend/test/ops/docs/data) instead of overloading one agent.
- This is the **current default pattern**, but Tao may change the rules as needs evolve.