From empire-research
Guides open-ended exploration by shallow-scanning 3-5 candidate approaches, deep-diving user-selected ones, and delivering a consolidated comparison with recommendation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/empire-research:exploreThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<section id="purpose-vs-compare">
explore when the solution space is open: user knows the problem, not the options/empire-research:compare instead when user already has a known set of options to evaluate head-to-head/empire-research:compare and confirm before proceeding hereAskUserQuestion with concrete optionsAfter problem confirmed, dispatch ONE research agent for broad enumeration
Agent names vary by environment; do not assume a specific agent exists
Inspect available subagents via the Agent tool's subagent_type parameter
Pick the available agent whose name/description best matches general research synthesis or broad information retrieval; if multiple candidates fit, prefer the most specific; if none fit, use the most general research-oriented agent available
Shallow agent instructions:
Enumerate 3–5 candidate approaches only
One short paragraph per approach — no deep evaluation
Required output format:
1. <Approach Name>
<One-paragraph description — what it is, how it addresses the problem>
2. <Approach Name>
...
Cap response under 300 words
Present shallow-scan output to user verbatim before proceeding
After approaches selected, dispatch the deep research one of two ways
Preferred — Workflow tool available:
Invoke the bundled deep-dive workflow; it fans out one researcher per approach with structured pros/cons/fit:
Workflow({
scriptPath: "${CLAUDE_PLUGIN_ROOT}/workflows/explore-deepdive.js",
args: { problem, constraints, successCriteria, approaches: [{ name, description }] },
})
Surface the workflow's log() lines as progress
Feed the returned approaches[] into consolidated-report
Skip agent-selection and parallel-deep-dispatch — the workflow owns dispatch
Fallback — Workflow tool unavailable: use agent-selection then parallel-deep-dispatch below
dispatch-mode)Agent tool's subagent_type parametersubagent_type value) + one-line rationale BEFORE dispatchSend single message with multiple Agent tool calls (one per approach)
Each agent receives:
Required deep agent output format:
Approach: <name>
Summary: <2-3 sentences>
Pros:
- <point>
Cons:
- <point>
Key Evidence / Citations:
- <source or concrete reference>
Fit Rating: <High / Medium / Low> — <one sentence rationale>
Cap each agent response under 500 words
stats.researched < stats.requested, MUST name the approaches that failed and ask whether to re-run them before presenting| Approach | Pros | Cons | Fit |
|---|---|---|---|
Conflicts section — where agents cite contradicting evidence; state each sideRecommended approach — prioritized pick with rationale; cite supporting evidenceexplore-deepdive workflow when the Workflow tool is available; else dispatch deep agents in parallel (single message, multiple tool uses)Creates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.
npx claudepluginhub marcoskichel/empire --plugin empire-research