staff-session

Multi-agent architectural planning uses tiered debaters to produce competing positions, which a dedicated synthesizer resolves into a final PM-gated output. You initiate this by running a plan mode command with your objectives and a specified execution tier.

Critiquing an existing artifact uses review mode to generate structured findings through configured debater tiers. A dedicated synthesizer resolves conflicts and produces a final PM-gated critique without taking on full implementation ownership.

Role separation in a staff session assigns competing positions to debaters while a dedicated synthesizer resolves conflicts into the final output. This ensures rigorous challenge and synthesis without the synthesizer assuming full implementation ownership.

Yes, lightweight routing supports single-reviewer dispatch for architectural plan generation. You can configure tiered dispatch to route between lightweight single-reviewer execution and standard or full multi-debater staff sessions.

PM-gated decisions are needed when coordinating multi-person architectural planning and review so PMs can delegate implementation details. This ensures final plans or findings are rigorously challenged by debaters and synthesized before approval.

Yes, staff-session satisfies deterministic team orchestration by applying strict routing rules for lightweight versus standard or full execution. It separates roles between debaters and a synthesizer to produce PM-gated synthesized outputs.