interpretive-orchestration

Examine philosophical assumptions and check for methodological coherence. Use when users question their philosophical stance, their language contradicts their declared epistemology, they are moving between stages and want to verify coherence, or something feels 'off' about their analytical approach. Checks language coherence, method-epistemology alignment, and AI relationship consistency.

Shared infrastructure for Interpretive Orchestration. Provides state management, configuration I/O, batched file operations, and enforcement utilities for qualitative research projects. Use when working with .interpretive-orchestration/config.json, checking stage completion, updating progress, or validating project setup.

Dialogical coding for qualitative research. Acts as thinking partner in Stage 1 (never suggests codes, only asks questions) and reflexive coding partner in Stage 2 (4-stage visible reasoning). Use when coding interview transcripts, field notes, or other qualitative data.

Initialize a new qualitative research project with Socratic onboarding. Guides researchers through philosophical foundation establishment via interactive dialogue. Use when starting a new project, setting up epistemic stance, or configuring methodological preferences.

Deep reasoning and paradox navigation via MCP tools. Integrates Sequential Thinking for systematic analysis and Lotus Wisdom for navigating contradictions. Use when planning complex analysis, working through theoretical tensions, or making methodological decisions.

Progress dashboard and navigation for Interpretive Orchestration. Shows current stage, progress indicators, next steps, and atelier status. Use when checking progress, navigating between stages, or planning next steps.

This skill should be used when users need to convert PDFs (especially with tables or figures), mentions 'convert', 'PDF', 'document processing', has complex academic papers to import, or asks about document conversion options.

This skill should be used when users have audio interview recordings to transcribe, need to convert PDF documents, mentions 'import data', 'transcribe', 'convert', or is starting data preparation for Stage 1 or Stage 2.

This skill should be used when users need to gather foundational literature, mentions 'literature review', 'theoretical patterns', 'Stream A', wants to search for academic papers, or is starting Stage 2 Phase 1 theoretical stream.

This skill should be used when users want to initialize a new qualitative research project, mentions 'setup', 'initialize', 'new project', 'getting started', or asks about establishing philosophical foundations and epistemic stance. Triggers on phrases like 'start my research project', 'create a new study', 'configure my stance'.

This skill should be used when users need to convert PDFs (especially with tables or figures), mentions 'convert', 'PDF', 'document processing', has complex academic papers to import, or asks about document conversion options.

This skill should be used when users ask about which AI model to use for coding, mentions 'cost', 'batch', 'API', 'configure analysis', wants to process multiple documents, or needs to understand model capabilities and costs for Stage 2.

This skill should be used when users are ready to start Stage 2 coding, asks about processing documents systematically, needs to track coding progress, wants to generate audit documentation, or mentions 'batch', 'coding session', 'systematic coding'.

This skill should be used when users question their philosophical stance, their language contradicts their declared epistemology, they are moving between stages and want to verify coherence, mentions 'assumptions', 'examine', 'coherent', 'consistent', or something feels 'off' about their analytical approach.

This skill should be used when users need to think through a complex analytical decision, asks 'how should I approach this?' or 'help me think through...', is stuck on a difficult coding boundary, needs to plan dimensional analysis, or is building theoretical frameworks in Stage 3.

This skill should be used when users are building or refining their Gioia data structure, mentions 'Gioia', 'data structure', 'themes', 'concepts', 'dimensions', '1st-order', '2nd-order', 'aggregate', or needs to validate/export their analytical hierarchy for publication.

This skill should be used when users mention 'generate rules', 'isolation rules', 'methodology preset', 'apply preset', 'saturation', 'am I saturated', 'branch', 'fork', 'explore alternative', 'team', 'add researcher', 'intercoder reliability', 'dashboard', 'show status', or after /qual-design completes.

This skill should be used when patterns seem contradictory but both feel true, user is stuck in either/or thinking, theoretical and empirical streams seem irreconcilable, or user mentions 'paradox', 'tension', 'contradiction', 'both/and'. Helps integrate opposites at a higher level.

This skill should be used when users ask 'where am I?', 'what is my progress?', mentions 'status', 'dashboard', 'progress', wants to know if they are ready for the next stage, or needs an overview of their project state.