# Meeting Orchestrator — One-Page Reference

## What it does

Use this skill to:
- run a multi-role meeting
- ask one role to judge a topic directly
- let AI suggest participants before you confirm them
- handle long background text in a staged way
- keep each speaker turn as a separate message

## Two modes

### 1) Meeting mode
Multiple roles discuss one topic.

Typical flow:
1. Give topic + background.
2. AI suggests roles.
3. You confirm or edit the roles.
4. The meeting starts.
5. Each role speaks in one standalone message.
6. You can interrupt or add context.
7. The meeting ends with a report.

### 2) Single-role mode
One role gives a direct opinion.

Typical flow:
1. Choose a role, like `real_powell`.
2. Give topic + optional context.
3. Read the role’s judgment.
4. Ask for a second pass if needed.

## Best role defaults

Start with:
- `real_powell`
- `gstack_commercial`
- `gstack_technical`
- `gstack_ux`

Add more specialized roles when the topic needs them.

## How to provide large background text

You can:
- paste it directly
- point to a file/document
- split it into sections
- ask AI to summarize it first

Recommended structure:
- problem statement
- current situation
- constraints
- options
- risks
- decision criteria

## Message style

Keep it simple:
- one role = one message
- one user interruption = one message
- one final report = one message

## What to do before starting

- make the topic clear
- provide enough background
- review AI’s role suggestions
- confirm the participant list
- then start the meeting

## Common mistakes

- too little context
- skipping role confirmation
- packing unrelated issues into one meeting
- expecting a vague topic to produce a sharp answer

## Short rule of thumb

Give the topic, give the background, let AI suggest roles, confirm them, then let the meeting run one speaker at a time.