coding-workflow skill
scriptsOrchestrates systematic document coding processes, tracks progress, and generates audit trails for qualitative research stages.
- GitHub stars
- 21
- Files
- 4
- Last commit
- Nov 6, 2026
- License
- —
- Allowed tools
- —
What does the coding-workflow skill do?
coding-workflow orchestrates systematic document coding processes, tracks progress, and generates audit trails for qualitative research stages.
Summary generated from the skill's SKILL.md.
About the coding-workflow skill
Qualitative researchers managing Stage 2 coding can use this skill to orchestrate systematic document processing and maintain rigorous audit trails. It functions by managing parallel streams of theoretical and empirical analysis, allowing an agent to move from foundational literature extraction to pattern characterization. The skill is designed for use once Stage 1 is complete and an initial data structure is established.
An agent should load this skill when starting a coding session, processing document batches, or needing to track progress through various statuses like pending, in-progress, or reviewed. It relies on specific scripts such as process-batch.js for document handling, track-documents.js for status monitoring, and generate-audit.js for creating documentation. The workflow integrates with the dialogical-coder agent and uses an interpretive-pause hook to enforce reflection breaks every five documents to ensure analytical depth.
What an agent can do with it
- 1Execute systematic document batchesRun a batch of specific documents through a coding phase using a designated agent.
- 2Monitor coding progressCheck the current status of all documents within a research project.
- 3Create research audit trailsGenerate a markdown file containing the audit documentation for the coding process.
- 4Verify project readinessConfirm that Stage 1 is finished and the project is ready for Stage 2 coding.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the coding-workflow skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the coding-workflow skill in Plugin
/plugin marketplace add linxule/interpretive-orchestration /plugin install interpretive-orchestration@interpretive-orchestration
Install the coding-workflow skill in Claude Code
~/.claude/skills/coding-workflow/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/coding-workflow ~/.claude/skills/coding-workflowInstall the coding-workflow skill in Claude Code (project)
.claude/skills/coding-workflow/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/coding-workflow .claude/skills/coding-workflowInstall the coding-workflow skill in Codex
~/.agents/skills/coding-workflow/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/coding-workflow ~/.agents/skills/coding-workflowInstall the coding-workflow skill in Gemini CLI
~/.gemini/skills/coding-workflow/SKILL.md
$ npx degit linxule/interpretive-orchestration/plugin/skills/coding-workflow ~/.gemini/skills/coding-workflowInstall the coding-workflow skill in Claude.ai
npx degit linxule/interpretive-orchestration/plugin/skills/coding-workflow coding-workflow && zip -r coding-workflow.zip coding-workflow # claude.ai → Customize → Skills → + → Create skill → Upload a skill → coding-workflow.zip
SKILL.md
View on GitHubScript paths:
${CLAUDE_PLUGIN_ROOT}below is this plugin's root folder, two levels above this skill's own folder. Claude Code fills it in. If you see it unfilled, still starting with a dollar sign (as in Codex, Copilot CLI or Kimi Code), put that folder's absolute path in its place before you run a command.
coding-workflow
Document coding orchestration for Stage 2. Manages the systematic coding process, tracks progress, and generates audit trails.
When to Use
Use this skill when:
- User is ready to start Stage 2 coding
- User asks about processing documents systematically
- User needs to track coding progress
- User wants to generate audit documentation
- User mentions "batch", "coding session", or "systematic coding"
Prerequisites
Before using this skill, verify:
- Stage 1 is complete (10+ documents manually coded)
- Initial data structure exists
- Project is properly initialized
Use ${CLAUDE_PLUGIN_ROOT}/skills/_shared/scripts/read-config.js --project-path <project folder> to check readiness.
Workflow Stages
Stage 2 Phase 1: Parallel Streams
Stream A (Theoretical)
- Analyze foundational literature
- Extract theoretical patterns
- Use @scholarly-companion for Socratic dialogue
Stream B (Empirical)
- Apply @dialogical-coder to documents
- Follow 4-stage visible reasoning
- Build evidence for concepts
Stage 2 Phase 2: Synthesis
- Compare theoretical and empirical patterns
- Identify alignments and tensions
- Refine data structure
Stage 2 Phase 3: Pattern Characterization
- Identify systematic variations
- Document pattern properties
- Prepare for Stage 3 theorizing
Scripts
process-batch.js
Process a batch of documents through coding workflow.
node "${CLAUDE_PLUGIN_ROOT}/skills/coding-workflow/scripts/process-batch.js" \
--project-path /path/to/project \
--documents "D001,D002,D003" \
--agent dialogical-coder \
--phase phase2_synthesis
track-documents.js
Track which documents have been coded and their status.
node "${CLAUDE_PLUGIN_ROOT}/skills/coding-workflow/scripts/track-documents.js" \
--project-path /path/to/project \
--list # List all documents and status
--mark-coded D004 # Mark document as coded
generate-audit.js
Generate audit trail documentation.
node "${CLAUDE_PLUGIN_ROOT}/skills/coding-workflow/scripts/generate-audit.js" \
--project-path /path/to/project \
--output audit-trail.md
Coding Session Flow
Recommended Session Structure
-
Pre-Session (5 min)
- Check config state:
read-config.js - Review recent conversation log
- Set session goals
- Check config state:
-
Coding (45-60 min)
- Process 5-10 documents with @dialogical-coder
- Full 4-stage reasoning for each
- Log interactions:
append-log.js
-
Reflection (10-15 min)
- Write analytical memo
- Update data structure if needed
- Note emerging questions
-
Post-Session
- Update progress:
update-progress.js - Queue documents for next session
- Update progress:
Interpretive Pauses
Every 5 documents, the system prompts:
"You've coded 5 documents. Before continuing, reflect:
- What patterns are emerging?
- Any surprises or tensions?
- Does the data structure still fit?"
This is enforced by the interpretive-pause.js hook.
Templates
conversation-log-spec.md
Specification for the JSONL log format used for AI-to-AI transparency.
Entry structure:
{
"timestamp": "ISO-8601",
"agent": "dialogical-coder",
"action": "coding",
"document_id": "D003",
"concept_id": "AD1_T1_C1",
"content": "Applied code with reasoning...",
"metadata": {}
}
Document Status Tracking
| Status | Meaning |
|---|---|
pending |
Not yet coded |
in_progress |
Currently being coded |
coded |
First pass complete |
reviewed |
Human has reviewed AI coding |
finalized |
Coding complete, quotes extracted |
Integration Points
- @dialogical-coder - Primary coding agent
- interpretive-pause hook - Enforces reflection breaks
- _shared scripts - State management
- gioia-methodology skill - Data structure validation
Related
- Commands: Various coding commands trigger this skill
- Agents: @dialogical-coder for visible reasoning
- Hooks: interpretive-pause.js, check-stage1-complete.js
- Other Skills: project-dashboard for progress visualization
Files in this skill
4coding-workflow skill questions
How do I install the coding-workflow skill in Claude Code?
Run npx degit linxule/interpretive-orchestration/plugin/skills/coding-workflow ~/.claude/skills/coding-workflow. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the coding-workflow skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What are the prerequisites for using the coding-workflow skill?
Before use, you must ensure Stage 1 is complete with at least 10 documents manually coded, an initial data structure exists, and the project is properly initialized.