How this command is triggered — by the user, by Claude, or both
Slash command
/content-intelligence:discover <category or keyword>The summary Claude sees in its command listing — used to decide when to auto-load this command
When the user invokes `/discover`, follow this process: ## 1. Search Brands Call `discover_brands` with the user's query. If the user's query is more about content examples than entities to track, also run `content_intelligence_search` in parallel — it searches the entire Adology database using AI aspect decomposition and can surface brands the user hasn't considered. ## 2. Present Results For each discovered brand, show: - **Name** — brand name - **Category** — industry or vertical - **Available platforms** — where they are active - **Relevance** — why this result matches the query F...
When the user invokes /discover, follow this process:
Call discover_brands with the user's query.
If the user's query is more about content examples than entities to track, also run content_intelligence_search in parallel — it searches the entire Adology database using AI aspect decomposition and can surface brands the user hasn't considered.
For each discovered brand, show:
Format as a numbered list so the user can reference items by number.
If content_intelligence_search returned results, present those separately as "Content examples from brands you might want to track" — the brand names on those items become additional discovery leads.
Prompt: "Which of these would you like to add to a knowledge set? Give me the numbers, or say 'all' to add everything."
Once the user selects:
list_knowledge_sets and ask)batch_add_feeds for multiple additions rather than calling add_feed one at a timeadd_feed is fineIf the user wants to fetch data immediately via trigger_fetch:
feedNames parameter for selective refresh rather than fetching the entire KSget_workflow_status to monitor scraping progressadd_feed with feedType: 'influencer'./analyze [brand]"get_workflow_status to check when data scraping is complete"npx claudepluginhub adologyai/content-intelligence-plugin --plugin content-intelligence/discoverRuns a full product discovery cycle: ideation, assumption identification and prioritization, and experiment design for a product or feature idea.
/discoverRuns a structured discovery flow from problem framing through opportunity mapping to validation planning, producing a discovery plan, prioritized assumptions, and experiment backlog.
/discoverRuns a multi-LLM orchestrated research probe on a given topic, dispatching parallel agents across providers for broad exploration.
/discoverRuns full user research cycle for a product or feature: creates 2-4 personas, empathy map, journey map, and summary with key insights and design implications.
/discoverExecutes evidence-based product discovery through customer interviews and assumption testing for a product concept, producing validation docs, lean canvas, interview logs, and wave decisions.
/discoverDiscovers NL programming artifact files in a directory by category (A: plugins, B: project config, F: memory), outputting classified list with paths, patterns, and line counts.