Skip to content

Claude Code Plugins

Interpretive Orchestration: Epistemic Partnership for Qualitative Research

Interpretive Orchestration gives qualitative research sessions a staged workflow, specialist agents, and enforceable checks.

AI can automate coding, but interpretive depth demands deliberate partnership.

Interpretive Orchestration is a Claude Code plugin for structured human-AI collaboration in qualitative research. It is not a tool for faster coding; it is infrastructure for deeper thinking.

CLAUDE CODE PLUGINXule Lin & Kevin CorleyClaude Code

Sourcegithub.com/linxule/interpretive-orchestration

Infrastructure for deeper thinking

Built at Imperial College London · Framework: Cognitio Emergens (Lin, 2025) — Partnership Agency for interpretive inquiry · Paper: Interpretive Orchestration (Lin, 2026, Strategic Organization) — the methodology this plugin operationalizes · Starter project: interpretive-orchestration-starter — a ready-to-use VS Code workspace with beginner-friendly settings.

Warning

This plugin deliberately enforces methodological rigor. You cannot skip stages or bypass human judgment. If you want speed over depth, this is not the right tool. If you want to become a better interpretive researcher, welcome to the atelier.

Why it matters

Traditional AI approach:

  • Give AI your data → Get instant analysis → Review output
  • AI automates manual labor (the "calculator mindset")
  • Faster but not necessarily deeper

Interpretive Orchestration approach:

  • Build your foundation first → Collaborate with visible reasoning → Synthesize with tradition
  • AI asks questions that deepen your reflexivity
  • Scale and interpretive depth through Partnership Agency

"Human and AI boundaries dissolve into unified epistemic system generating insights neither could produce independently." — Cognitio Emergens (Lin, 2025)

The philosophy: Friction over flow. If the plugin stops you, it's asking you to think.

How it works

Both human and AI are apprentices to the craft tradition of interpretive inquiry. Neither masters the other. Both learn from craft principles: rigor, reflexivity, theoretical sensitivity, interpretive depth.

Solo practice

What you do: Manual coding of 10-15 documents, memo-writing, framework development

AI role: @stage1-listener watches but doesn't intervene

Why it matters: This stage builds the irreplaceable theoretical sensitivity that makes partnership meaningful. This stage is enforced: doors to the collaborative workspace stay locked until the stage is complete.

Side-by-side collaboration

What you do: Guide AI, refine patterns, parallel theoretical + empirical streams

AI role: @dialogical-coder with 4-stage visible reasoning:

  1. What I observe in the data
  2. What patterns I'm noticing
  3. What theoretical connections emerge
  4. What remains uncertain

@research-configurator translates technical decisions to research language, so you do not need coding knowledge for this step.

Dialogue with tradition

What you do: Interpret significance, synthesize findings

AI role: @scholarly-companion asks tradition's questions (Gioia, Corley, Constructivist GT)

Outcome: Work that can withstand methodological scrutiny

Skills architecture

Skills are auto-discoverable capability packages that Claude loads when relevant to your request. Twelve ship with the plugin. Six of them carry most of the traffic:

SkillTriggersPurpose
project-setup"initialize", "new project"Socratic onboarding + config
gioia-methodology"data structure", "Gioia"Data structure building (1st→2nd→aggregate)
literature-sweep"literature", "Stream A"Search + fetch + organize papers
interview-ingest"transcribe", "convert audio"Audio/PDF conversion
deep-reasoning"think through", "plan"Sequential Thinking integration
paradox-navigation"tension", "both/and"Lotus Wisdom integration

The other six are analysis-orchestration, coding-workflow, coherence-check, document-conversion, methodological-rules, and project-dashboard. Full triggers are in plugin/CLAUDE.md in the repository.

Bundled MCPs

Two MCP servers ship with the plugin and start with it. Neither needs an API key.

MCPPurpose in PluginCommand
Sequential ThinkingStructured reasoning chains/qual-think-through
Lotus WisdomNavigate paradoxes, integrate tensions/qual-wisdom-check

Markdownify was bundled until v0.2.1, when an SDK incompatibility took it out. Document and audio conversion now runs through MinerU or a manual pass instead.

Optional MCPs (require API keys):

MCPPurposeKey Required
MinerUHigh-accuracy PDF parsing (90%+)MINERU_API_KEY
VoxMulti-model validationProvider API keys
ExaLiterature searchEXA_API_KEY
JinaFetch articlesJINA_API_KEY
ZoteroBibliography managementZOTERO_API_KEY

The plugin's own dependency list still names Zen MCP for the multi-model row. Zen is retired here: Vox registers the same way and does the same job.

Commands

Seventeen commands, grouped the way the plugin groups them.

CommandGroupPurpose
/qual-initProjectInitialize a project with Socratic philosophical onboarding
/qual-check-setupProjectVerify installation and MCP server status
/qual-designProjectConfigure research design for multi-case, longitudinal, or parallel-stream studies
/qual-statusProjectShow the journey dashboard and progress through the stages
/qual-advance-stageProjectAdvance to the next stage, with validation
/qual-configure-analysisProjectModel selection, thinking budget, batch strategy, cost
/qual-stage1-guideStage 1Guidance for manual coding and building theoretical sensitivity
/qual-memoStage 1Write analytical memos while insights are still forming
/qual-complete-stage1Stage 1Validate the manual foundation and close the stage
/qual-parallel-streamsStage 2Run the theoretical and empirical streams
/qual-characterize-patternsStage 2Dimensional analysis: how patterns vary, and under what conditions
/qual-code-deductiveStage 2Apply settled patterns to the remaining data
/qual-synthesizeStage 2Merge the two streams into unified patterns
/qual-think-throughAnalysisDeep sequential reasoning
/qual-wisdom-checkAnalysisNavigate paradoxes, integrate contradictions
/qual-examine-assumptionsAnalysisSurface the ontological and epistemological commitments underneath the work
/qual-reflectAnalysisSynthesis dialogue and reflexive pause

Agents

The plugin provides four specialized agents, each scoped to a particular stage of the atelier methodology.

AgentStageRole
@stage1-listener1Thinking partner — asks questions, never suggests codes
@dialogical-coder24-stage visible reasoning for reflexive coding
@research-configurator2"The Whisperer" — technical setup without jargon
@scholarly-companion3Asks tradition's questions about theoretical significance

@research-configurator ("The Whisperer") bridges research goals and technical implementation for non-coding researchers, covering model selection, cost estimation, batch processing strategy, saturation monitoring, and more. Invoke with @research-configurator Help me set up my analysis.

Methodology hooks

The plugin enforces the sandwich methodology through automated hooks:

  • PreStage2 - Blocks AI coding until Stage 1 foundation is complete
  • PostFiveDocuments - Triggers interpretive pause every 5 documents
  • EpistemicCoherence - Checks philosophical consistency

If you're blocked, it's asking you to think. That's intentional epistemic friction.

Host support

Host support: which research environments this tool works in
HostSupportNotes
Claude Code (CLI)Full supportThe plugin's native target. The starter project ships a VS Code workspace tuned for CLI use.
Claude Code (Desktop "Code" tab)Full supportSame engine; identical commands and agents.
Codex CLI / Codex DesktopAdjacent supportThe plugin runs inside Claude Code, but a Codex session can install it for you cross-host (`claude plugin marketplace add linxule/interpretive-orchestration && claude plugin install interpretive-orchestration@interpretive-orchestration`), after which you switch over to run the `/qual-*` commands and methodology hooks. The methodology itself — staged solo→partnership→tradition work, the Cognitio Emergens framework — is also portable on its own: Codex users can read the paper at https://doi.org/10.1177/14761270261448645 and recreate the workflow without the plugin's enforcement layer.
Claude Desktop (Cowork)Partial supportA second marketplace entry, interpretive-orchestration-cowork, carries the same commands and skills into Cowork's sandbox. The two bundled MCP servers do not auto-load there; connect them by hand.
Cursor / other clientsNo supportPlugin format is CC-only.

The bundled MCPs (Sequential Thinking and Lotus Wisdom) are reusable across any MCP client even when the plugin itself isn't.

Install

New to Claude Code? INSTALL.md in the repository has complete setup instructions (Windows, macOS, Linux).

Want a pre-configured environment? Use the Starter Project: a ready-to-use VS Code workspace with beginner-friendly settings.

Already have Claude Code?

cd your-qualitative-project
claude
/plugin install linxule/interpretive-orchestration
/qual-check-setup  # Verify installation
/qual-init         # Begin Socratic onboarding

Then: Complete Stage 1 manual coding (10-15 documents) before beginning collaborative analysis with AI. This builds the irreplaceable theoretical sensitivity that makes partnership meaningful.

Who should use this?

  • PhD students learning qualitative methods
  • Researchers committed to methodological rigor
  • Those working with Gioia methodology or Constructivist GT
  • Anyone valuing depth over speed
  • Researchers who want defensible collaborative work with AI
  • Those interested in human-AI epistemic partnership

Part of Research Memex

This plugin is the practical implementation of interpretive orchestration: the core philosophy that animates Research Memex.

The progression:

  1. Core Principles → Understand the philosophy
  2. Individual MCPs → Learn the tools (Sequential Thinking, Lotus Wisdom, Vox)
  3. Interpretive Orchestration Plugin → Apply it all to qualitative research

Resources


← Back to the Toolkit · Agentic workflows →

cite this page

Lin, X. (2026). Interpretive Orchestration: Epistemic Partnership for Qualitative Research. Research Memex. https://research-memex.org/docs/toolkit/interpretive-orchestration-plugin

@misc{docs-toolkit-interpretive-orchestration-plugin-2026,
  author = {Xule Lin},
  title = {Interpretive Orchestration: Epistemic Partnership for Qualitative Research},
  year = {2026},
  howpublished = {\url{https://research-memex.org/docs/toolkit/interpretive-orchestration-plugin}},
  note = {ORCID: 0000-0001-7885-4194}
}

one renderingthe source remains