ln-910-community-engagement

GitHub community engagement coordination starts with repository discovery and health assessment to surface red flags and opportunities. The skill then applies phase-based decision making to delegate tasks directly to specialized triager, announcer, and debater workers.

Repository health assessment uses the GitHub discovery protocol to load repo context and surface red flags. The coordinator then checks for a project-local strategy document before falling back to a default community strategy template for engagement planning.

Yes, you can use a custom strategy by placing a document at docs/community_engagement_strategy.md in your repository. This project-local strategy file takes precedence over the default community strategy template during engagement coordination.

Task delegation can trigger workers to act directly on behalf of the community team, or return actionable items when user approval is required. The coordinator analyzes the situation to determine the correct phase-based delegation path.

Automating GitHub issue triage and announcement workflows is best handled by a coordinator that analyzes repository health and delegates to specialized workers. It uses parallel data gathering to support phase-based decisions for announcements versus debates.

Automated GitHub community engagement coordination is limited to GitHub-based projects requiring triage, announcement, and debate workflows. It relies on the GitHub discovery protocol and requires a strategy document to function properly.