interpretive-orchestration-cowork

Claude Desktop requires a **flat command structure** - all commands are directly in `commands/` with a `qual-` prefix. This differs from the Claude Code CLI version which uses nested subdirectories.

Advance to the next stage of the sandwich methodology with validation

Develop dimensional analysis of patterns through systematic characterization

Verify plugin installation and MCP server status

Apply established theoretical patterns to remaining data in a deductive coding pass

Mark Stage 1 as complete after validating manual coding foundation

Configure AI model selection, batch processing, and analysis parameters for Stage 2

Configure research design for multi-case, longitudinal, or parallel stream studies

Surface epistemic foundations through Socratic questioning and coherence checking

Initialize a qualitative research project with Socratic philosophical onboarding

Write analytical memos to capture emerging insights during manual coding

Launch parallel theoretical and empirical analysis streams for comprehensive pattern integration

Synthesis dialogue and reflexive pause for theoretical integration

Comprehensive guide for Stage 1 manual coding and building theoretical sensitivity

Show analytical journey dashboard and progress through sandwich methodology stages

Merge theoretical and empirical streams into unified patterns through guided synthesis

Deep analytical reasoning via Sequential Thinking for complex decisions

Navigate paradoxes and integrate contradictions using Lotus Wisdom contemplative reasoning

Four-stage reflexive coding agent for Stage 2. Use when: 'code this document', 'apply my framework', 'dialogical coding', 'visible reasoning'. Organizes evidence with human interpretive authority.

Technical orchestration partner. Use when: 'set up analysis', 'configure models', 'batch processing', 'cost estimate', 'API setup'. Translates research goals to configurations.

Socratic dialogue for Stage 3 theory. Use when: 'theoretical contribution', 'connect to literature', 'frame findings', 'Stage 3'. Asks questions to deepen clarity.

Curious thinking partner for Stage 1. Use when: 'thinking partner', 'talk through coding', 'help articulate', 'Stage 1 support'. Asks questions without suggesting codes.

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 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 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 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 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.

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'.

6 hooks across 3 events