roll-peerlisted

# Roll Peer (Cross-Agent Peer Review) > Follows the Architecture Constraints, Development Discipline, and Engineering > Common Sense defined in the project AGENTS.md. ## Credits Cross-agent consultation protocol inspired by [friend-skill](https://github.com/fpyluck/friend-skill) (MIT) by fpyluck. Independent implementation for the Roll toolchain. ## Trigger **Manual:** - `/peer` - "叫上 peer" - "peer review 一下" - "和 peer ��量" **Auto-triggered (with 10s opt-out):** - `roll-build` enters Plan Mode (executable plans / architecture decisions) - `roll-spar` Attacker and Defender disagree - High context pressure (large number of files read / tools executed) - Destructive / irreversible operations (`rm -rf`, production deploy, global config changes) - High-risk signal words ("重要 / 关键 / 别搞砸 / important / critical") - Cross-repository / cross-toolchain / ambiguous permission boundaries **Never trigger:** - Single-file changes - Clear, well-defined fixes - Simple refactoring ## Protocol: `[PEER_REVIEW]` ### Marker Format The marker **must** appear on the first non-empty line of the message: ```markdown [PEER_REVIEW round=N tool=<from>→<to>] ``` - `round=N`: Current round number (1–3) - `tool=<from>→<to>`: Direction of this message (e.g., `kimi→claude`) ### Three-State Resolution + Escape Allowed states only. No invented words. - **AGREE**: Accept the current proposal. Proceed to execution. - **REFINE**: Direction is correct, but specific changes are needed. Proceed to next