audience-impact

When assessing a change, ask: who is on the other end, and how fast does this reach them?

This skill provides a mental model — not an exhaustive ledger. Use it to reason about which audiences a change affects, then load the catalog skills for detailed surface tracing when needed.

When multiple audiences are affected, address them in pipeline order: immediate impacts first (Contributor), then versioned impacts (Builder — changeset + migration guide), then deployed impacts (Platform User — QA), then infrastructure (Self-hosted — docs). This matches the natural merge → publish → deploy sequence.

此變化會影響誰以及如何影響他們？映射受眾（角色 × 部署模式）以影響傳播 - 立即、下一次發布、下一次部署或靜默。 在規劃、實施或審查變更時使用，以了解受眾的影響範圍。 補充產品表面積和內部表面積（對現有的內容進行分類；這項技能告訴您誰在乎）。 觸發因素：誰受到影響、爆炸半徑、重大變更、受眾、角色、影響分析、所需的變更集、所需的文件。 來源：inkeep/agents。