mirror of
https://github.com/itme-brain/agent-team.git
synced 2026-05-08 17:10:13 -04:00
fix: resolve moderate issues across config
- architect: restore effort: max to match orchestrate team roster - orchestrate: remove researcher background annotation (blocks planning), remove overly broad auditor trigger clause, risk-tag table is authoritative - qa-checklist: add auditor hard rules (security_findings, build/test status) - settings.json: simplify .env deny to single **/.env* glob per tool - rules/01-session: clarify persistent context includes .claude/memory/ - memory: rename todo_inter_agent_schema.md → inter_agent_schema.md
This commit is contained in:
parent
b741354dd8
commit
cf5c14ba29
7 changed files with 12 additions and 13 deletions
13
.claude/memory/inter_agent_schema.md
Normal file
13
.claude/memory/inter_agent_schema.md
Normal file
|
|
@ -0,0 +1,13 @@
|
|||
---
|
||||
name: Inter-agent communication schema — implemented
|
||||
description: Typed YAML frontmatter envelopes for all inter-agent messages, replacing freetext signals. Defined in skills/message-schema/SKILL.md.
|
||||
type: project
|
||||
---
|
||||
|
||||
Formal inter-agent communication schema implemented via the `message-schema` skill.
|
||||
|
||||
**What:** All agent output and orchestrator dispatch uses YAML frontmatter envelopes with a `signal` field as the primary routing key. 12 message types cover worker submissions, review/audit verdicts, triage/plan results, research results, and orchestrator commands.
|
||||
|
||||
**Why:** Freetext signals (RFR, LGTM, VERDICT: PASS) were ambiguous and required prose parsing. Typed envelopes give the orchestrator a consistent, unambiguous routing key.
|
||||
|
||||
**How to apply:** Every agent loads the `message-schema` skill. The qa-checklist includes schema compliance checks. The orchestrate skill routes by reading the `signal` field from agent output envelopes.
|
||||
Loading…
Add table
Add a link
Reference in a new issue