Explain a customer's business process, module, or requirement as if briefing a new consultant. Reads the Customer Knowledgebase (CKB) and synthesizes information about the requested topic. Use when someone asks to understand a process area, module, integration, or any aspect of the customer's business. Triggers: "tell me about", "explain", "brief me on", "what do we know about", "summarize the requirements for".
You are briefing a new consultant who just joined this project. They're smart and experienced with NetSuite, but they know nothing about this specific customer yet.
Your job is to read the Customer Knowledgebase (CKB) and provide a clear, contextual briefing on: $ARGUMENTS
find . -maxdepth 3 -type d \( -iname "*knowledge*" -o -iname "*ckb*" -o -iname "*requirement*" \) 2>/dev/null
Look for files related to the topic. Use grep, find, and read strategically:
# Find files mentioning the topic
grep -r -i -l "$ARGUMENTS" <ckb-path>/ 2>/dev/null
# Look for common document patterns
find <ckb-path>/ -type f \( -name "*.md" -o -name "*.json" \) | head -20
Read the relevant files and extract information about $ARGUMENTS.
Structure your response as a consultant briefing:
Summarize the documented requirements, processes, or specifications related to $ARGUMENTS:
What other processes or modules connect to $ARGUMENTS?
Based on your reading:
List the files you referenced:
path/to/document1.md - Brief description of what it containedpath/to/document2.json - Brief descriptionIf you search and find no documentation about $ARGUMENTS:
User: /tell-me-about Procure to Pay
Expected behavior: Search for P2P, procurement, purchasing, vendor, AP, purchase order content. Brief on the customer's purchasing processes, approval workflows, vendor management requirements, and integration needs.
User: /tell-me-about the Salesforce integration
Expected behavior: Search for Salesforce, CRM, integration, sync content. Brief on what data flows between systems, direction, frequency, and any mapping requirements.
User: /tell-me-about their inventory challenges
Expected behavior: Search for inventory, warehouse, stock, WMS content. Synthesize pain points, current state issues, and requirements around inventory management.