define-audiences

Identifies stakeholders and documents evaluation criteria for reviewer sub-agent design.

Updated Aug 27, 2026

Search Tags:#governance #mapping #reviewers #stakeholders #sub-agent #audiences

Ready to run

npx skills add https://github.com/SujinHwang27/agent-os-lab --skill define-audiences

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: define-audiences
Source: https://github.com/SujinHwang27/agent-os-lab/tree/main/agent-os-factory-v2.0/.claude/skills/define-audiences
Command: npx skills add https://github.com/SujinHwang27/agent-os-lab --skill define-audiences

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies all audiences that evaluate the user's output and documents their priority signals, conflicts, and decision rules to streamline reviewer governance.

Core Features & Use Cases

Audience profiling: Enumerate primary, gatekeeper, technical, and internal evaluators with concrete evaluation criteria.
Conflict mapping: Capture where audiences disagree and how to resolve these tensions.
Sub-agent mapping: Propose candidate sub-agents and trigger points to operationalize reviews within a workflow.

Quick Start

Define the complete audience model for your current project and export it to domain-input/audiences.md.

Frequently Asked Questions about define-audiences

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I map stakeholders and resolve conflicts for output review?▼

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.

How do I set up reviewer sub-agents to automate evaluation workflows?▼

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.

What is audience profiling in product governance and when do I need it?▼

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.

How do I document evaluation criteria for different types of reviewers?▼

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.

Can I use this approach for complex workflows with competing stakeholder priorities?▼

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.

What format should the audience model output be exported to?▼

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.