persona-panel-orchestration

Consult named Personas independently and synthesize their perspectives into a recommendation.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/rickvang/Persona-Library --skill persona-panel-orchestration-rickvang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: persona-panel-orchestration
Source: https://github.com/rickvang/Persona-Library/tree/main/.agents/skills/persona-panel-orchestration
Command: npx skills add https://github.com/rickvang/Persona-Library --skill persona-panel-orchestration-rickvang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Comparing multiple expert perspectives on a decision often collapses into generic consensus or invented viewpoints. This Skill runs structured consultations with explicitly named Personas, processes each one independently, and preserves real disagreement so recommendations stay evidence-backed and attributable. ## Core Features & Use Cases - Single Persona, Panel, and Playbook Modes: Consult one named Persona, a panel of two to four, or a named Playbook with defined stages and participants. - Independent Perspective Processing: Each Persona is loaded and analyzed separately before comparison, keeping priorities, evidence, and uncertainty distinct. - Shared Collaboration Runs: Multi-Persona build or decision sessions use a named problem-context record with attributable contributions, dispositions, and a solution-quality gate. - Read-Only Safety: The Skill inspects records and synthesizes advice without mutating Personas, Docs, Decisions, or generated files; durable artifacts require explicit authorization. - Use Case: A product lead asks two named Personas to review a roadmap tradeoff. The Skill loads both records, summarizes each perspective independently, names where they agree and disagree, and returns a concise recommendation with a next action. ## Quick Start Use $persona-panel-orchestration to consult Personas Alice and Bob on whether to prioritize the onboarding redesign, and compare their evidence and disagreements.

Frequently Asked Questions about persona-panel-orchestration

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

FAQPage Schema
How do I consult multiple Personas on a decision?▼

Name two to four Personas explicitly and state your goal, decision, and constraints. The Skill loads each record independently, compares their evidence and disagreements, and returns a synthesized recommendation with a next action.

How do I run a panel consultation without inventing participants?▼

Participant selection must be explicit in your request. The Skill never infers or adds Personas; if a named participant's record is unavailable, it reports that limitation instead of simulating the perspective.

Can persona-panel-orchestration update records or save artifacts?▼

No, the Skill is read-only and only inspects records to synthesize advice. Saving a Draft, Doc, or Proposed Decision is a separate explicitly authorized operation handled through the reconciliation protocol.

What happens when Personas disagree during a panel?▼

Disagreement is preserved rather than smoothed into consensus. The output names which Persona supports each material point, lists tradeoffs and unresolved questions, and states what evidence would change the recommendation.

When should I use a named Playbook instead of a panel?▼

Use a named Playbook when the session has explicitly defined participants, stages, artifacts, and decision rights. The Skill loads the Playbook structure and reports missing participants or stage evidence instead of inventing them.

What are the limitations of multi-Persona collaboration runs?▼

Shared runs require a named problem-context document as the handoff key, and the coordinator is the single writer. A run cannot close while contributions are pending disposition or the solution-quality gate has not passed.