Skip to content

How to Use Party Mode

Use Party Mode to get multi-agent feedback on any artifact or decision point in the DLC.

  • Evaluating an ARC for blind spots
  • Getting multi-perspective feedback on bolt specs
  • Any point where you want more than one expert opinion
cat-party-mode

You’ll be asked what you want to discuss. Provide context — the more specific, the better:

“Review this ARC for our password reset feature. I’m concerned about the security constraints — are they sufficient?”

After any content-generating step, choose P from the A/P/C menu. The current artifact is automatically provided as context.

Party Mode brings relevant agents into a discussion. Each agent responds in character with their domain expertise:

  • 🎯 Clara (PI) focuses on intent alignment and stakeholder needs
  • 🏗️ Julian (SA) evaluates architecture and constraints
  • Marcus (Dev) assesses implementability and practical concerns
  • 🔍 Vera (QA) checks for testing gaps and compliance risks
  • 📝 Tullia (Tech Writer) reviews clarity and documentation quality
  • 📊 Livia (Analyst) provides business and research context

Not all agents participate in every roundtable — CAT selects the relevant ones based on the topic.

After the roundtable:

“Accept these changes? (y/n)”

  • Yes — The suggested improvements are incorporated into the artifact
  • No — The original artifact is preserved as-is

You can also selectively accept changes by saying: “Accept Julian’s and Vera’s suggestions but keep the original scope from Clara’s perspective.”

  1. Be specific about what you want reviewed. “Review my ARC” is less useful than “Review my ARC’s security constraints for a payment integration.”

  2. Use it at phase transitions. Before moving from Intent to Architecture, or Architecture to Construction, a roundtable catches issues early.

  3. Don’t overuse it. Party Mode adds depth but also time. Use it for high-stakes decisions, not every minor artifact.


See Also: Use Advanced Elicitation · Agent Reference · Getting Started