Multi-perspective — e11-multi-perspective

A round-table: the installed Foundry agents (or a custom roster) talk to each other and to you about the artifact or question at hand, like distinct people in a lively room. The skill orchestrates; the perspectives collide; you harvest.

When to use it

• A decision or draft deserves more than one professional lens — PRD scope calls, architecture trade-offs, naming, a risky plan.
• You want an AI focus-group panel over customer data or a persona set.
• Retrospectives use it under the hood — e11-retrospective runs the epic review on this roster.
• Not for generating volume ideas (Discovery) or hardening one idea (Forge idea).

How to invoke

[MP] from a menu, or invoke e11-multi-perspective ("roundtable", "multi-perspective mode"). At start it:

1. Resolves the roster via its resolve-roster.mjs — the configured default group if set, else the installed agents from central config [agents.*] (with a fallback to the legacy agent manifest on older installs).
2. Shows who's in the room (icon, name, one-line role) and which other groups exist.
3. Asks what to get into — unless the invocation already said.

Mid-session you can switch rooms (--roster <id>), summon a specific member by name, or name an inline cast ("get me a skeptical CFO and a support rep") — an inline cast is the roster for that session.

Rosters and memory

• Custom rosters and personas live in your overrides — members and groups are customize.toml data, so a team panel ("our ICP customers") is a .foundry/custom/e11-multi-perspective.toml edit or an [agents.<code>] addition in central config. The skill's create-roster flow authors these for you conversationally.
• Per-roster memory (when memory_enabled): each roster keeps a memlog under its memory dir, so the panel remembers previous sessions' positions and running jokes. Delete the memlog to reset the room.

Gotchas

• It's a discussion, not a vote. The output is sharpened understanding and named disagreements — decisions stay yours (or go to the owning skill).
• Empty roster on fresh installs — if central config's agents table resolves empty, the skill tells you and improvises; run install again or configure a group.
• Keep the artifact in front of the room. Point the session at a file; abstract prompts get abstract theater.

Customization

.foundry/custom/e11-multi-perspective.toml — default_roster, custom members/groups, orchestration_mode, memory_enabled, memory dir. See Customization.

Source

e11-multi-perspective/SKILL.md (with scripts/resolve-roster.mjs and the roster references)

See also: Discovery · Forge idea · Agents quick-reference.