ayao-workflow-agent

Summary

ayao-workflow-agent provides event-driven multi-agent coding orchestration for OpenClaw. It dispatches Codex and Claude Code agents using tmux, automatically tracks model token usage, manages task state, and sends notifications (including Telegram alerts) on workflow events.

Included Assets

• AGENTS.md: Guidance and workflow for session management and agent roles.
• MEMORY.md: Curated, long-term memory for the agent (context, project info).
• SOUL.md: Defines the assistant’s personality, boundaries, and working principles.
• TOOLS.md: Local environment/configuration notes for hardware or specific tools.
• skills/coding-swarm-agent/projects/README.md: Project context and task record-keeping guide.
• docs/agent-swarm-playbook.md: Best practices for multi-agent coding orchestration.
• memory/*: Daily logs and context snapshots for continuity.
  • Project traces (e.g., install events, Codex/Claude setup, session logs)
  • Issue debugging notes (e.g., OpenClaw lag, model switch logs)
  • Auto-update process and user-assistant chats

How to Use

1. Session Startup

   • Always begin by reading SOUL.md (personality and boundaries).
   • Review MEMORY.md (long-term context) and the latest memory/YYYY-MM-DD.md (today + recent history).
   • Use AGENTS.md to orient on agent roles, session practices, and memory handling.

2. Workflow

   • The agent manages task distribution to tmux sessions running Codex/Claude workers.
   • Token usage for each agent run is tracked automatically.
   • Task completion triggers updates: state persistence, follow-up task unlocking, and end-user notifications.
   • Notifications and alerts (e.g., dispatch events, pipeline status) can be sent to Telegram for real-time updates.

3. Customize/Extend

   • Use TOOLS.md for your own environment specifics (device names, SSH aliases, etc.).
   • Review or adapt the agent orchestration guidelines in docs/agent-swarm-playbook.md.
   • For project-specific context, maintain documentation under skills/coding-swarm-agent/projects/.

Notes

• Token and task state tracking are handled via scripts and log routines.
• Telegram integration requires bot credentials and chat/channel ID configuration.
• All agent personality, context, and operational details should be adjusted by editing the provided Markdown (SOUL.md, MEMORY.md, etc).
• Daily context and technical notes are stored by date for review and retrospection.
• This workspace is purely Shell-based and engineered for event-driven operation within the OpenClaw ecosystem; no web interface or external persistence is included by default.