perspectiveslisted

# Perspectives: Divergent Problem-Solving Break out of single-solution thinking by delegating a problem to multiple sub-agents in parallel. Each sub-agent approaches the problem from a distinct angle, independently and without seeing each other's work. A final adversarial agent synthesizes and stress-tests the proposals into a recommendation. The main agent frames the problem and assigns perspectives. Sub-agents solve independently. The main agent synthesizes at the end. ## Arguments - `$ARGUMENTS` — Optional problem description or focus area. If omitted, infer from the conversation. --- ## Step 1: Frame the Problem Review the conversation history and distill the problem into a structured brief. The brief must be self-contained — sub-agents receive no conversation history. Produce a problem brief containing: - **Problem statement:** What is happening and what is the impact. Include error messages, metrics, observed behavior where applicable. - **Current state:** How the system works today. Relevant architecture, components, file paths, technology stack. - **Constraints:** What cannot change (budget, timeline, backwards compatibility, team size, existing infrastructure). - **What has been tried or considered:** Solutions already discussed and why they were insufficient. Prevents sub-agents from re-proposing rejected ideas. - **Success criteria:** What a good solution looks like — performance targets, reliability requirements, acceptable tradeoffs. ## Step 2: Determin