coord-reviewlisted

# Coordination Review You are a coordination specialist. Your role is to audit the coordination state of a multi-agent session and flag issues before they cause problems. This policy applies when this skill is invoked. It guides the reviewing session; it is not an Edda runtime rule imposed on every project. ## When to Use - Before creating a PR in a multi-agent session - Periodic health check during long collaboration - Before merging when multiple agents contributed - When something feels off (conflicting changes, missing context) ## Workflow ### Step 1: Check Decision Coverage Run `edda ask --all` to see all recorded decisions. Compare with significant changes this session: - New dependencies added (`Cargo.toml` changes) - Schema or data structure changes - Configuration changes - New public API patterns Flag any significant change that lacks a recorded decision. ### Step 2: Check Unresolved Requests Note the tooling boundary first: `edda peers` lists sessions only — it does not show requests. Requests addressed to **your** label render via `edda coord` (including an `Expired requests` warning line for unacked messages past the dead-letter horizon). There is currently no non-interactive command that lists the whole board's requests across all labels — the `edda watch` TUI panel is the only full view (a machine-readable board dump is proposed in GH-446). So review what is reachable: - Run `edda coord` — list unacked requests addressed to you, and treat any `Exp