tmpl/multi-agent-mux
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: rename AGENT.md to MULTI_AGENT_RULES.md and consolidate INSTRUCTION.md into AGENTS.md

Browse Source 
- .agents/AGENT.md -> .agents/MULTI_AGENT_RULES.md
- .agents/AGENT.ko.md -> .agents/MULTI_AGENT_RULES.ko.md
- INSTRUCTION.md -> AGENTS.md (root-level)
- Update create_session.sh onboarding prompt to reference new path
- All cross-references in BOOTSTRAP.md/.ko.md, README.md/.ko.md, SKILL_FEATURES.md updated
- Fix document title headers (# AGENT.md -> # MULTI_AGENT_RULES.md, # CLAUDE.md -> # AGENTS.md)
This commit is contained in:
Godopu
2026-07-09 12:04:25 +09:00
parent 2b9bb39d6f
commit 0fa09b4d90
10 changed files with 36 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
BOOTSTRAP.md
+4 -4
View File
@@ -11,8 +11,8 @@ A new agent can follow the steps in this guide sequentially to establish a stabl
Before cloning this project into a new environment, you must first understand the locations and roles of its core components:
* `.agents/`: Orchestration and custom agent skills root.
* `AGENT.md`: Definition of agent roles (PM, Worker, Reviewer) and event publication rules.
* `AGENT.ko.md`: Definition of agent roles (PM, Worker, Reviewer) and event publication rules (Korean).
* `MULTI_AGENT_RULES.md`: Definition of agent roles (PM, Worker, Reviewer) and event publication rules.
* `MULTI_AGENT_RULES.ko.md`: Definition of agent roles (PM, Worker, Reviewer) and event publication rules (Korean).
* `skills/`: A collection of shell scripts that execute multi-agent coordination and asynchronous job processing.
* `lib.sh`: The core orchestration shell functions and virtual environment (venv) auto-loading library.
* `multi-agent-mux-create/`: Script to launch isolated tmux agent sessions.
@@ -80,7 +80,7 @@ Open the generated `.env` file to configure settings as needed.
> [!WARNING]
> **Security Mode Default Warning**:
> The system's default setting is the **unauthenticated PoC mode**. If an `auth_token` is not explicitly provided (or is `null`) during job registration, HMAC signature verification is skipped.
> In a public broker environment or production phase, you must generate and inject a unique random `auth_token` during job registration to enable HMAC signature security. (For detailed security protocols, refer to section `2.3 Security Protocol` in [MESSAGING.md](./MESSAGING.md) and [AGENT.md](.agents/AGENT.md). Automated token generation and injection via CLI is on the roadmap under task `FW-N6`.)
> In a public broker environment or production phase, you must generate and inject a unique random `auth_token` during job registration to enable HMAC signature security. (For detailed security protocols, refer to section `2.3 Security Protocol` in [MESSAGING.md](./MESSAGING.md) and [MULTI_AGENT_RULES.md](.agents/MULTI_AGENT_RULES.md). Automated token generation and injection via CLI is on the roadmap under task `FW-N6`.)
---
@@ -181,6 +181,6 @@ rm -f ".mam/jobs/$JID.json" ".mam/jobs/$JID.lock"
## 7. Onboarding Collaborating Agents (New Agent Onboarding)
Once the setup is verified, onboarding agents should immediately read the **[AGENT.md](.agents/AGENT.md)** guidelines in the .agents/ directory.
Once the setup is verified, onboarding agents should immediately read the **[MULTI_AGENT_RULES.md](.agents/MULTI_AGENT_RULES.md)** guidelines in the .agents/ directory.
The guidelines describe essential workflows—such as **surgical change constraints, cross-verification review loops, and pane snapshotting to prevent viewport truncation**—allowing new agents to quickly and safely integrate with the multi-agent workflow.