Ln 910 Community Engagement

Paths: File paths (references/, ../ln-*) are relative to this skill directory.

ln-910-community-engagement

Type: L2 Coordinator (active) Category: 9XX Community Engagement

Analyzes current community health and repository state, consults the engagement strategy, and delegates to the appropriate worker. Each worker is also invocable standalone.

Overview

Phase 0: GitHub Discovery

MANDATORY READ: Load references/community_github_discovery.md

Execute the discovery protocol. Extract:

• {owner}/{repo} for all GitHub operations
• repo.id for GraphQL mutations (passed to workers)
• maintainer login (authenticated user)
• Discussion category IDs

Gate checks: gh authenticated? Discussions enabled?

Load strategy: check docs/community_engagement_strategy.md in target project, fallback to references/community_strategy_template.md.

Phase 1: Situation Analysis

If $ARGUMENTS contains a direct action keyword (announce, debate, triage, respond), skip analysis and jump to Phase 3 (Direct Delegation).

Otherwise, gather context from multiple sources in parallel:

1a. Community Health

Delegate to triager in summary mode (no interactive preview):

Skill(skill: "ln-911-github-triager", args: "summary")

Extract from triager output: red flags, priority counts (P0/P1/P2), health metrics.

1b. Unreleased Changes

# Last announcement date: most recent Announcements discussion
gh api graphql -f query='query($owner: String!, $name: String!) {
  repository(owner: $owner, name: $name) {
    discussions(first: 1, categoryId: "{categories.Announcements}", orderBy: {field: CREATED_AT, direction: DESC}) {
      nodes { createdAt title }
    }
  }
}' -f owner="{owner}" -f name="{repo}"

Then check what changed since:

git log --oneline --since="{last_announcement_date}"

Read CHANGELOG.md — any entries newer than the last announcement?

1c. Cadence Check

From strategy Section 4:

• Days since last announcement → monthly digest overdue if >30 days?
• Any pending architectural decisions that need RFC?

Phase 2: Decision Matrix

Apply strategy Section 1 (Announcement vs Debate) to the gathered context:

Output: Situation Report

Present to user:

## Community Status — {YYYY-MM-DD}

**Repo:** {owner}/{repo}
**Last announcement:** {date} ({days} days ago)
**Open items:** {issues} issues, {prs} PRs, {discussions} discussions

### Red Flags
{list or "None"}

### Recommended Action
{One of: Announce / Debate / Respond to items / No action needed}

**Reason:** {brief explanation based on strategy criteria}

Wait for user approval before proceeding.

Phase 3: Delegate

After user approves the recommended action:

Direct Delegation (when $ARGUMENTS specifies action)

Analysis-Based Delegation

Shared References

Strategy Override

Each target project can override the default strategy by creating docs/community_engagement_strategy.md. All skills check project-local first, then fall back to the template in references/.

Phase 4: Meta-Analysis

Optional reference: load references/meta_analysis_protocol.md only when the user asks for post-run meta-analysis or protocol-formatted run reflection.

Skill type: planning-coordinator. When requested, run after Phase 3 completes. Output to chat using the planning-coordinator format.

TodoWrite format (mandatory):

- GitHub discovery (in_progress)
- Situation analysis (pending)
- Apply decision matrix (pending)
- Invoke ln-911-github-triager (pending)
- Invoke ln-912-community-announcer (pending)
- Invoke ln-913-community-debater (pending)
- Invoke ln-914-community-responder (pending)
- Report outcome to user (pending)

Worker Invocation (MANDATORY)

Host Skill Invocation: Skill(skill: "...", args: "...") is mandatory delegation.

• Claude: call the Skill tool exactly as shown.
• Codex: if no Skill tool exists, locate the named skill in available skills, read its SKILL.md, treat args as $ARGUMENTS, execute that skill workflow, then return here with its result/artifact.
• Do not inline worker logic or mark the worker complete without executing the target skill.

All workers: Invoke via Skill tool — workers see coordinator context.

Definition of Done

• GitHub discovery complete (owner/repo, categories, maintainer extracted)
• Situation analyzed (health + unreleased changes + cadence) OR direct delegation triggered
• Decision matrix applied with priority-based action selection
• Worker delegated or recommendations shown to user
• User informed of outcome

Version: 1.0.0 Last Updated: 2026-03-13