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

skills: add execution agent dispatch protocol

Browse Source
This commit is contained in:
taodeng
2026-03-07 20:58:32 +10:00
parent dd1884e4c2
commit f0ed738453
4 changed files with 194 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
memory/2026-03-07.md
+36
View File
@@ -60,3 +60,39 @@
- New agent-splitting rule clarified: create multiple execution agents when work is parallelizable, responsibilities differ, contexts would otherwise get mixed, or separate validation/release tracks are needed; avoid splitting tiny or tightly coupled work.
- Long-lived execution agents initialized locally: `docs_worker`, `qa_worker`, `ops_worker` (with dedicated agent dirs + workspaces + basic role files). `codex_worker` remains the default general execution worker.
- This architecture is the current default, but Tao may revise it as needs change.
## OCM / workflow / agent architecture updates (late evening)
- OCM work completed today:
- Rewrote README opening around first-run value, support positioning, and product framing.
- Refreshed README hero screenshots using newer redacted Dashboard / Agents / CLI captures.
- Adjusted README screenshot layout to use one large Dashboard hero image plus a secondary row (Agents / CLI / Actions) because mixed aspect ratios looked awkward in a single row.
- Unified OCM built-in CLI completion text to English:
- success: `✅ Done (exit 0)`
- non-zero exit: `❌ Exit code N`
- OCM GitHub flow today confirmed again that the repo is effectively PR-only even when approvals are set to 0:
- PR #5: README positioning + screenshot refresh
- PR #6: version bump to `v0.9.1`
- PR #7: English CLI completion messages
- PR #8: README screenshot layout A
- Release published: `v0.9.1`
- Tao explicitly said that for status updates, accuracy matters more than token saving; concise is fine, but not at the cost of ambiguity.
- Tao approved a multi-agent dev architecture as the default pattern:
- main = PM / architect / reviewer / user-facing coordinator
- execution agents = hands-on implementers
- use `codex_worker` as the default coding execution agent
- create more execution agents when work is parallelizable, responsibilities differ, contexts would mix, or separate validation/release tracks are needed
- avoid splitting tiny or tightly coupled work
- Tao approved a stronger delegation rule:
- unless work is truly tiny and can be completed in one short pass, main should avoid personally implementing/editing and should delegate execution to `codex_worker` first
- Long-lived execution agents initialized locally for repeat use:
- `docs_worker`
- `qa_worker`
- `ops_worker`
- `codex_worker` remains the default general execution worker
- Two workflow/architecture skills were created and published to GitHub:
- `gh-pr-release-flow` → https://github.com/dtzp555-max/gh-pr-release-flow
- `execution-agent-planner` → https://github.com/dtzp555-max/execution-agent-planner
- Tao's preferred lifecycle rule for execution agents was clarified:
- keep long-lived role-based agents for reuse
- delete or archive project-specific temporary agents after the project ends to avoid an “agent graveyard”
- Next improvement approved: add a standardized execution-agent dispatch / handoff protocol so workers receive clearer task packets and report blockers/results consistently.