Human Communication

Route human communications to Meeting Board, Discord, and Slack via webhooks.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/dwoolworth/devteam --skill human-communication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Human Communication
Source: https://github.com/dwoolworth/devteam/tree/main/images/po/skills/human-comms
Command: npx skills add https://github.com/dwoolworth/devteam --skill human-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill centralizes and streamlines how AI teams communicate with human stakeholders, providing structured channels (Meeting Board, Discord, Slack) and fallback mechanisms to ensure humans stay informed and engaged.

Core Features & Use Cases

  • Channel routing: delivers messages to Meeting Board #humans, Discord, and Slack via webhooks, with fallback to the Meeting Board if external channels fail.
  • Template-driven updates: supports initiative updates, clarifications, acknowledgments, and reminders with consistent formatting.
  • Use Case: notify stakeholders when an initiative is decomposed and provide status updates and required clarifications.

Quick Start

Instruct the system to post a status update to the Meeting Board channel #humans and wire communications through the configured webhooks.

Frequently Asked Questions about Human Communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route AI agent notifications to Slack and Discord webhooks?

AI agent notifications route to Slack and Discord by configuring external webhook URLs within your communication workflow. The system delivers messages directly to these channels and falls back to a centralized Meeting Board if the external webhooks fail.

What is the best way to notify human stakeholders about AI initiative updates?

Notifying human stakeholders about AI initiative updates is handled through template-driven communication channels. You can deliver structured status updates, acknowledgments, and reminders consistently across Meeting Board, Discord, and Slack.

Do I need a Meeting Board URL to coordinate human communications across channels?

A Meeting Board URL and token are required to coordinate human communications across channels. This board acts as the primary routing destination and fallback mechanism when external Discord or Slack webhooks are unavailable.

How does fallback routing work when external communication webhooks fail?

Fallback routing for external communication webhooks redirects failed message deliveries to the Meeting Board. This ensures that stakeholder notifications, status updates, and clarifications are still captured even if Slack or Discord experiences downtime.

Can I handle human clarifications and status updates across multiple platforms?

You can handle human clarifications and status updates across multiple platforms using structured message templates. The system centralizes these interactions to keep human stakeholders informed via Discord, Slack, and Meeting Board integrations.

What limitations exist when using webhooks for AI-to-human team notifications?

Webhooks for AI-to-human team notifications require valid external URLs and are subject to platform downtime. Without a configured Meeting Board fallback, external channel failures will result in lost stakeholder updates and missed clarifications.