In this article
Project Planning/Community Interaction
| Field | Value |
|---|---|
| Kind | instruction |
| Source | .github/instructions/project-planning/community-interaction.instructions.md |
| Invocation | Applied automatically to **/.github/agents/project-planning/backlog-manager.agent.md, **/.github/agents/project-planning/subagents/github-backlog-executor.agent.md, **/.github/skills/project-planning/backlog-management/references/github.md |
| Interactive | No |
What it does
Community interaction voice, tone, and response templates for GitHub-facing agents and prompts
When to use it
Use these conventions when composing or posting contributor-visible GitHub issue, pull request, or discussion responses through the backlog workflow. Select the matching scenario, apply content-policy guards, and post the reason before a state change; escalate cases that require maintainer judgment rather than forcing a template.
Example usage
Provide a concrete example that shows the asset in action, including representative input and the resulting output.