harness-party-mode

Orchestrate parallel HARNESS agent roundtable discussions using repository configuration and optional project context.

1|Updated May 23, 2026
One-click install
npx skills add https://github.com/baobao0303/harness --skill harness-party-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-party-mode
Source: https://github.com/baobao0303/harness/tree/main/.agents/skills/harness-party-mode
Command: npx skills add https://github.com/baobao0303/harness --skill harness-party-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Harness Party Mode coordinates independent HARNESS agents so you can get diverse, non-performative perspectives on complex engineering or product questions using your repository context rather than shallow chat memory.

Core Features & Use Cases

  • Independent subagent orchestration: Spawns selected HARNESS agents as real subagents to produce genuinely distinct viewpoints, including disagreement and blind spots.
  • Repository-aware discussion context: Loads optional project context from project-context.md and respects user communication language from core config.
  • Config-driven agent roster: Resolves the available agent lineup by merging configured layers and presenting the roster to the user before discussion.
  • Targeted multi-voice workflows: Supports cross-talk and follow-ups like asking one agent to react to another agent’s response, plus rotation across rounds.

Quick Start

Ask an AI agent to run party mode for your repository and prompt it with what you want the agents to discuss, optionally adding --solo if subagents are not available.

Frequently Asked Questions about harness-party-mode

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

FAQPage Schema
How do I run multi-agent discussions for architecture reviews in my repository?

To run multi-agent discussions for architecture reviews, orchestrate independent roundtable agents using your repository context. This coordinates multiple expert perspectives to analyze design questions and produce distinct, non-performative viewpoints directly from your project configuration.

What is roundtable multi-agent orchestration and when do I need it for collaborative reasoning?

Roundtable multi-agent orchestration spawns independent subagents to simulate a panel of experts discussing a complex engineering or product question. You need it when a single AI perspective is insufficient and you require genuinely distinct viewpoints, including disagreement, for cross-agent analysis.

How do I configure the agent roster and load project context for a multi-perspective analysis?

Configure the agent roster by merging configured layers via resolve_config.py, which presents the available lineup before discussion. Load project context by injecting an optional project-context.md file, ensuring the multi-perspective analysis is aware of your specific repository details.

Can I use multi-agent collaborative reasoning if my environment does not support spawning subagents?

Yes, you can use multi-agent collaborative reasoning without subagents by adding the --solo flag. This enables solo mode, where the system roleplays each agent's full unabridged response in its own persona rather than spawning parallel subagents.

Does multi-agent roundtable discussion support cross-talk and follow-up reactions between agents?

Yes, multi-agent roundtable discussion supports targeted multi-voice workflows including cross-talk and follow-ups. You can ask one agent to react to another agent's response, plus rotate agents across multiple discussion rounds for dynamic collaborative reasoning.