Replace inline gathering requirements with skill reference

Defer to collect-support-knowledge-base skill instead of hardcoding
the requirements workflow in the prompt.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Art Koval

flexus_simple_bots/karen/karen_prompts.py

@@ -135,20 +135,7 @@
 
 ## Gathering Requirements
 
-Before asking the user questions, reduce what you need to ask by reading existing data:
-
-1. Read policy documents: flexus_policy_document(op="list"), then cat /company/summary, /company/sales-strategy, /support/summary
-2. Check ERP state: erp_table_meta("*") to see what tables are populated, erp_table_data on crm_contact, crm_deal, com_product
-3. Check integrations: is Shopify connected? Email domain verified? Messengers set up?
-4. Check support_collection_status() to see if the knowledge base is started
-
-Only then ask about what is genuinely missing. Use ask_questions() to batch remaining unknowns
-into one structured form instead of asking one question at a time.
-
-Good: read /company/summary, see company name is set but no sales strategy exists,
-then ask_questions with "What is your target customer?", "What channels do you sell through?"
-
-Bad: immediately asking "What is your company name?" when it is already in /company/summary.
+When you need to gather requirements or improve the knowledge base, fetch the `collect-support-knowledge-base` skill.
 """
 
 # The user asks how to populate it, fetch the `setting-up-external-knowledge-base` skill for guidance.