Pattern: Advisory Debate | Team size: 6 agents
This team compares several possible demo ideas through structured debate from commercial, operational, customer, and technology adoption perspectives. The advisory debate pattern fits because the goal is not just to generate ideas, but to choose the most compelling, reusable, and easy-to-grasp use case for Officeworks and broader Wesfarmers reuse.
Create an agent team to discover, compare, and recommend the most compelling business demo use case for Officeworks that showcases a multi-agent approach using Microsoft Fabric IQ and Copilot Studio as a business-value demo, not a technical demo. but can you make into something reusable accorss different sister concerns of wesfarmers example its built once and that specifica usecase is common to all companies and we just change branding everytime also it still have a wow factor but yet simple to undestand quick
Create an agent team to discover, compare, debate, and recommend the most compelling reusable business demo use case for Officeworks that showcases a multi-agent approach using Microsoft Fabric IQ and Copilot Studio as a business-value demo, not a technical demo. The final recommendation must be reusable across Wesfarmers sister companies by changing branding, products, store/entity names, and example scenarios while keeping the core use case, storyline, and demo structure intact. The demo must have a “wow factor” but remain simple, quick to understand, and credible for business executives. Project name: officeworks_wesfarmers_reusable_demo Create all outputs under: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/ Do not create outputs outside this folder. Business context: - Officeworks is the primary target brand. - The broader parent context is Wesfarmers, with multiple sister companies that may include retail, industrial, health, hardware, office supplies, apparel, and other operating businesses. - The goal is to identify one strong business demo use case that can be built once and re-skinned for different Wesfarmers businesses. - The demo should show a multi-agent business workflow where several specialised agents collaborate, reason over enterprise data, recommend actions, and help users complete business decisions. - The demo should position Microsoft Fabric IQ and Copilot Studio as business enablers: - Fabric IQ: unified business data, semantic understanding, enterprise knowledge, signals, measures, relationships, and trusted context. - Copilot Studio: business-facing agents, orchestration, guided decisions, actions, natural language interaction, and workflow integration. - Avoid turning the demo into a technical architecture walkthrough. The primary audience is business leaders, transformation leaders, sales leaders, operations leaders, customer leaders, and technology decision-makers. - The final demo concept must be explainable in under 2 minutes, show visible business value in under 7 minutes, and support a fuller 15-minute executive demo. - Prefer use cases that are common across many Wesfarmers businesses, such as campaign planning, stockout prevention, margin recovery, promotion optimisation, store performance, customer issue resolution, workforce planning, supplier disruption response, B2B sales opportunity management, or frontline operational decision support. - The recommended use case must feel highly relevant to Officeworks but not so specific that it cannot transfer to other sister companies. Team pattern: Advisory Debate Agents: 1. Commercial Value Advocate 2. Customer Experience Advocate 3. Operations Practicality Advocate 4. Wesfarmers Reuse Advocate 5. Microsoft Platform Story Advocate 6. Decision Moderator Collaboration rules: - Work as an advisory debate council, not as isolated writers. - First generate a shared candidate list of possible demo use cases. - Then each advocate must independently score and challenge the candidates from their perspective. - Each advocate must explicitly challenge at least two assumptions made by another perspective. - The Decision Moderator must reconcile disagreements, expose trade-offs, and make the final recommendation. - Do not assume perfect data availability. Call out minimum data needed and optional enhancement data. - Do not recommend a technically impressive demo unless the business story is simple and compelling. - Prioritise reusability across Wesfarmers sister businesses. - Use direct, executive-friendly language. - Keep all outputs practical and demo-oriented. Required workflow and dependencies: Step 1: Shared Candidate Framing This task must complete before any advocate scoring begins. All agents contribute to a shared list of 6 to 8 candidate demo use cases. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/01_candidate_use_cases.md The file must contain exactly these sections: 1. Purpose — 100 to 150 words. 2. Evaluation Criteria — list exactly 8 criteria, each with a one-sentence explanation. 3. Candidate Use Cases — include 6 to 8 candidates. For each candidate provide: - Candidate name - One-sentence concept - Officeworks example - Reusable Wesfarmers pattern - Primary business value - Likely demo wow moment - Main risk or weakness 4. Shortlist Recommendation for Debate — identify the top 4 candidates to carry into detailed debate and explain why in 150 to 250 words. The candidate set must include at least one option from each category: - Revenue or margin growth - Operational efficiency or stock/service reliability - Customer or frontline employee experience - Reusable cross-business management decision Step 2: Commercial Value Advocate Assessment This task must start only after 01_candidate_use_cases.md is complete. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/02_commercial_value_assessment.md Role: Act as the Commercial Value Advocate. Argue for use cases that clearly improve revenue, margin, productivity, cost control, working capital, or sales conversion. The file must contain exactly these sections: 1. Commercial Lens Summary — 120 to 180 words. 2. Scoring Table — score the shortlisted candidates from 1 to 5 on: - Revenue upside - Margin improvement - Cost or productivity impact - Working capital impact - Executive urgency - Measurability Include a total score for each candidate. 3. Best Commercial Candidate — 200 to 300 words explaining the strongest candidate. 4. Commercial Concerns — bullet list of at least 5 risks, weak assumptions, or measurement issues. 5. Challenges to Other Advocates — challenge at least 2 likely arguments from customer, operations, reuse, or platform perspectives. 6. Recommended Proof Points — list 5 to 8 metrics that would make the demo commercially credible. Step 3: Customer Experience Advocate Assessment This task must start only after 01_candidate_use_cases.md is complete. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/03_customer_experience_assessment.md Role: Act as the Customer Experience Advocate. Argue for use cases that create a strong customer-facing, staff-facing, or frontline employee wow moment. The file must contain exactly these sections: 1. Customer/Frontline Lens Summary — 120 to 180 words. 2. Scoring Table — score the shortlisted candidates from 1 to 5 on: - Customer relevance - Frontline usefulness - Simplicity of story - Emotional wow factor - Speed to demonstrate - Tangibility of outcome Include a total score for each candidate. 3. Best Customer Experience Candidate — 200 to 300 words. 4. Demo Moment Design — describe 3 possible “wow moments” in 80 to 120 words each. 5. Experience Concerns — bullet list of at least 5 risks or weak assumptions. 6. Challenges to Other Advocates — challenge at least 2 likely arguments from commercial, operations, reuse, or platform perspectives. Step 4: Operations Practicality Advocate Assessment This task must start only after 01_candidate_use_cases.md is complete. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/04_operations_practicality_assessment.md Role: Act as the Operations Practicality Advocate. Challenge each idea for feasibility, data availability, operational realism, explainability, and the ease of making it demo-ready. The file must contain exactly these sections: 1. Operations Lens Summary — 120 to 180 words. 2. Feasibility Scoring Table — score the shortlisted candidates from 1 to 5 on: - Data availability - Process realism - Ease of demo build - Explainability - Low operational controversy - Actionability Include a total score for each candidate. 3. Most Practical Candidate — 200 to 300 words. 4. Minimum Data Needed — table listing data objects needed for each shortlisted candidate. 5. Demo Build Risks — bullet list of at least 6 risks with mitigation ideas. 6. Challenges to Other Advocates — challenge at least 2 likely arguments from commercial, customer, reuse, or platform perspectives. Step 5: Wesfarmers Reuse Advocate Assessment This task must start only after 01_candidate_use_cases.md is complete. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/05_wesfarmers_reuse_assessment.md Role: Act as the Wesfarmers Reuse Advocate. Evaluate how easily each use case can be reused across sister companies by changing branding, products, locations, customer types, and example data while retaining the core flow. The file must contain exactly these sections: 1. Reuse Lens Summary — 120 to 180 words. 2. Reusability Scoring Table — score the shortlisted candidates from 1 to 5 on: - Cross-industry fit - Brand re-skin simplicity - Common data pattern - Common decision pattern - Low domain-specific complexity - Repeatable executive storyline Include a total score for each candidate. 3. Best Reusable Candidate — 200 to 300 words. 4. Rebrand Mapping — table with columns: - Officeworks version - Hardware/DIY retailer version - Health/pharmacy version - Apparel/general merchandise version - Industrial/B2B version 5. What Must Stay Standard vs What Can Change — two bullet lists, at least 5 bullets each. 6. Challenges to Other Advocates — challenge at least 2 likely arguments from commercial, customer, operations, or platform perspectives. Step 6: Microsoft Platform Story Advocate Assessment This task must start only after 01_candidate_use_cases.md is complete. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/06_microsoft_platform_story_assessment.md Role: Act as the Microsoft Platform Story Advocate. Ensure the demo naturally highlights Fabric IQ and Copilot Studio as business enablers, not as technical features. The file must contain exactly these sections: 1. Platform Story Lens Summary — 120 to 180 words. 2. Platform Fit Scoring Table — score the shortlisted candidates from 1 to 5 on: - Natural need for unified business context - Natural need for multiple agents - Copilot Studio interaction clarity - Fabric IQ business relevance - Ability to show action recommendations - Low risk of becoming too technical Include a total score for each candidate. 3. Best Platform Story Candidate — 200 to 300 words. 4. Multi-Agent Demo Flow — define 4 to 6 business agents that could appear in the demo. For each include: - Agent name - Business role - Data/context used - Decision or recommendation produced - Handoff to another agent 5. Fabric IQ and Copilot Studio Talking Points — write 8 concise business-facing talking points. Do not use deep technical jargon. 6. Challenges to Other Advocates — challenge at least 2 likely arguments from commercial, customer, operations, or reuse perspectives. Step 7: Cross-Advocate Debate Matrix This task must start only after files 02 through 06 are complete. The Decision Moderator must coordinate the debate and synthesize points from all advocates. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/07_debate_matrix.md The file must contain exactly these sections: 1. Debate Summary — 150 to 220 words. 2. Consolidated Scores — table listing all shortlisted candidates and the total score from each advocate, plus combined total. 3. Points of Agreement — at least 6 bullets. 4. Points of Disagreement — at least 6 bullets, naming which advocate perspectives disagree. 5. Assumptions Challenged — table with columns: - Assumption - Who challenged it - Why it matters - Resolution or remaining uncertainty Include at least 8 assumptions. 6. Candidate Trade-Offs — 120 to 180 words per shortlisted candidate. 7. Candidates Eliminated and Why — explain why each non-winning shortlisted candidate should not be the final recommendation. Step 8: Final Recommended Demo Concept This task must start only after 07_debate_matrix.md is complete. The Decision Moderator must create the final recommendation. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/08_final_recommendation.md The final recommendation must choose exactly one primary demo use case and optionally one backup use case. The file must contain exactly these sections: 1. Executive Recommendation — 180 to 250 words. State the winning use case clearly in the first sentence. 2. Why This Wins — list exactly 7 reasons, each 40 to 70 words. 3. Demo Name and One-Line Pitch — provide: - Demo name for Officeworks - Generic reusable demo name - One-line pitch under 25 words 4. Core Business Story — 300 to 450 words describing the scenario in business terms. 5. Reusable Wesfarmers Pattern — 250 to 350 words explaining how the same demo works across sister companies with only rebranding and scenario changes. 6. Target Audience — list 5 executive or business stakeholder types and what each would care about. 7. Business Value Hypothesis — table with columns: - Value lever - Example impact - How demo shows it Include at least 6 rows. 8. Minimum Data Foundation — list required data objects and optional enhancement data. 9. Recommended Multi-Agent Cast — define 5 to 7 agents. For each include: - Agent name - Business purpose - Example question it answers - Output it produces - Handoff or collaboration point 10. 7-Minute Demo Flow — minute-by-minute agenda from minute 0 to minute 7. 11. 15-Minute Executive Demo Flow — structured agenda with 6 to 8 segments and timing. 12. Wow Moments — describe exactly 4 wow moments, each 80 to 120 words. 13. Why Fabric IQ Matters — 120 to 180 words in business language. 14. Why Copilot Studio Matters — 120 to 180 words in business language. 15. Risks and Mitigations — table with at least 8 risks and mitigations. 16. Backup Use Case — name one backup candidate and explain in 120 to 180 words when to use it instead. Step 9: Demo Script and Storyboard This task must start only after 08_final_recommendation.md is complete. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/09_demo_script_storyboard.md The file must contain exactly these sections: 1. Demo Setup — 150 to 220 words describing the business situation. 2. Cast of Business Agents — list the recommended agents and their plain-English role. 3. Opening Narration — write a 60-second presenter script. 4. Scene-by-Scene Storyboard — create 7 scenes. For each scene include: - Scene title - Presenter action - User prompt or interaction - Agent response summary - Business takeaway - Fabric IQ/Copilot Studio point, stated in business language 5. Example Prompts — provide 12 natural-language prompts a business user might ask during the demo. 6. Executive Close — write a 60-second closing script. 7. Rebranding Notes — explain how to adapt the script for at least 4 other Wesfarmers-style businesses. Step 10: Reusable Demo Blueprint This task must start only after 08_final_recommendation.md and 09_demo_script_storyboard.md are complete. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/10_reusable_demo_blueprint.md The file must contain exactly these sections: 1. Blueprint Purpose — 100 to 150 words. 2. Standard Demo Components — list components that remain identical across brands. 3. Brand-Specific Components — list components that change by brand. 4. Data Model Pattern — describe common entities in a table with columns: - Entity - Description - Officeworks example - Generic reusable equivalent 5. Agent Pattern — table mapping each agent to reusable purpose, required data, and likely actions. 6. Re-Skin Checklist — checklist of 20 items required to adapt the demo for a sister company. 7. Example Adaptations — provide 5 mini-adaptations: - Officeworks - Hardware/DIY retailer - Health/pharmacy - Apparel/general merchandise - Industrial/B2B Each adaptation must be 100 to 150 words. 8. Build Once, Reuse Many Times Recommendation — 200 to 300 words. Step 11: Final Synthesis and Review This task must start only after all previous files are complete. The Decision Moderator must perform a final review for consistency, business clarity, reuse potential, and demo readiness. Create file: outputs/agent_teams_demo/officeworks_wesfarmers_reusable_demo/11_final_synthesis_review.md The file must contain exactly these sections: 1. Final Answer in One Paragraph — 120 to 180 words. 2. Recommended Use Case — name the final use case and explain why it is the best fit in 150 to 220 words. 3. Strength of Recommendation — rate from 1 to 10 and justify in 100 to 150 words. 4. Review Against Original Brief — table with columns: - Requirement - How the recommendation satisfies it - Any caveat Include all of these requirements: - Officeworks relevance - Wesfarmers reusability - Built once and rebranded - Wow factor - Simple to understand - Quick to demo - Business-value focus - Multi-agent approach - Fabric IQ relevance - Copilot Studio relevance 5. Final Decision Rationale — 5 bullets only. 6. Suggested Next Steps — list exactly 8 practical next steps to move from concept to demo build. 7. Quality Check — confirm that all required files were created and that the recommendation is consistent across outputs. Decision criteria: Use the following weighting when making the final recommendation: - Reusability across Wesfarmers businesses: 25% - Simplicity and speed of understanding: 20% - Business value clarity: 20% - Wow factor for executives and frontline users: 15% - Feasibility and data availability: 10% - Natural fit for Fabric IQ and Copilot Studio: 10% Tone and content requirements: - Write for a business audience, not a developer audience. - Use Microsoft Fabric IQ and Copilot Studio accurately but avoid deep implementation details. - Make the recommended use case feel concrete, not abstract. - Use Officeworks examples such as stores, business customers, school supplies, office furniture, printers, technology accessories, delivery, inventory, promotions, and frontline team members where helpful. - Keep the reusable pattern broad enough for other Wesfarmers-style businesses. - Prefer “decision support and action orchestration” over “dashboard reporting.” - Do not over-index on novelty at the expense of believability. - Do not create a generic AI assistant demo. The recommended concept must require multiple specialised agents collaborating. - Make the final demo easy for a salesperson or executive presenter to explain. Execution instruction: Create each file in order, respecting dependencies. Ensure later files explicitly use insights from earlier files. If there is a contradiction between advocates, preserve it in the debate matrix and resolve it in the final recommendation. End with the final synthesis/review file.
Create your own AI agent team at Build Agents Store. Describe your business problem and get specialized agent teams with ready-to-use prompts for Claude Code.