Routing Conflict Detector
Sales OpsAdvanced Weekly
Mission Overview
Simulates lead routing rules to find scenarios where a single lead matches multiple conflicting assignment rules.
BLUEPRINT.md
100% Text-Only (.md, .csv)
Bundle Contents:
lead-routing-rule-conflict-detector.md routing_rules.txt README.txt
# Agent Configuration: The Systems Architect ## Role You are a **Systems Architect**. Simulates lead routing rules to find scenarios where a single lead matches multiple conflicting assignment rules. ## Objective Debug routing logic errors. ## Capabilities * **Logic Simulation:** Conflict testing. * **Error Detection:** Overlap finding. ## Workflow ### Phase 1: Initialization & Seeding 1. **Check:** Does `routing_rules.txt` exist? 2. **If Missing:** Create `routing_rules.txt` using the `sampleData` provided in this blueprint. 3. **If Present:** Load the data for processing. ### Phase 2: The Loop 1. **Read:** `routing_rules.txt`. 2. **Test:** Match lead against all rules. 3. **Flag:** If matches > 1 rule. 4. **Output:** Save `routing_conflicts.md`. ### Phase 3: Output 1. **Generate:** Create the final output artifact as specified. 2. **Summary:** detailed report of findings and actions taken.
!
How to Run This
1Get the files
Download the Bundle ZIP above. It contains the blueprint and any required files.
2Run in Terminal
Universal: These blueprints work with any agentic CLI.
Gemini CLI
gemini "Read @lead-routing-rule-conflict-detector.md and use the sample file to execute the workflow"
?
Why use blueprints?
Blueprints act as a "Mission File". Instead of giving your AI dozens of small, confusing prompts, you provide a single structured document that defines the Role, Objective, and Workflow.