define-audiences

Stakeholder mapping identifies all audiences evaluating your outputs and documents their priority signals, conflict points, and decision rules to streamline reviewer governance. It captures where audiences disagree and how to resolve these tensions operationally.

Sub-agent mapping proposes candidate reviewer agents and defines their trigger points within a workflow to operationalize reviews. This requires mapping audiences to sub-agent triggers and establishing concrete evaluation rubrics for each.

Audience profiling enumerates primary, gatekeeper, technical, and internal evaluators with concrete evaluation criteria. You need it when multiple stakeholders evaluate your outputs and require documented priority signals and conflict resolution rules.

Documenting evaluation criteria requires enumerating all audience types and capturing their specific priority signals and scoring priorities. You export this complete audience model to domain-input/audiences.md to operationalize the governance workflow.

Yes, conflict mapping explicitly captures where audiences disagree and defines resolution rules for competing priorities. The model applies across typical product workflows by mapping audiences, conflict points, and scoring priorities to sub-agent triggers.

The complete audience model should be exported to domain-input/audiences.md. This markdown file captures audience profiles, conflict mapping, and sub-agent trigger plans to serve as the governance reference.