Using Markdown Files as Workflow Engine for Claude Code in Kubernetes

A developer has implemented an unconventional workflow engine using plain English markdown files that Claude Code executes within Kubernetes. Instead of traditional pipeline definition tools like Dagster, Prefect, or Argo, they use markdown files named SKILL.md that contain simple instructions.
How It Works
The system runs Claude Code as a Kubernetes CronJob. The workflow logic is defined in markdown files written in plain English, with instructions like "scan Reddit, then classify, then create a PR." This approach allows non-technical team members, such as the developer's boss, to write pipeline logic directly.
Claude Code follows these markdown instructions and coordinates workflow steps by writing artifacts to disk. The developer reports running this system for more than a month with better stability than expected, though they note the debugging experience is rough and there's no guarantee of consistent behavior.
Practical Considerations
The developer suggests this approach works best for low-stakes pipelines where the tradeoff between simplicity and reliability is acceptable. They question whether this plain language instruction method would work for more difficult tasks or if it only succeeds because their use case is non-critical.
A full tutorial with a forkable example is available at everyrow.io/blog/claude-code-workflow-engine, providing a practical implementation reference for others interested in this approach.
📖 Read the full source: r/ClaudeAI
👀 See Also

Building an AI Code Review CLI with Claude: A Non-Traditional Pathway
GrandCru is a code review CLI developed by a former military officer using Claude AI. It features dual-channel Zod schema for technical feedback and creative prose.

Claude Code Used to Reverse Engineer Disney Infinity 1.0, Breaking 13-Year Character Restriction
A developer used Claude Code (Opus 4.6 with high reasoning) to reverse engineer the Disney Infinity 1.0 game binary, identifying and patching 13 validation call sites that prevented characters from playing in any playset. The solution required 17 binary patches and 3 modified data files, solving a problem the modding community had been unable to crack for over a decade.

Non-technical user's OpenClaw experience: setup friction overshadows automation benefits
A solo consultant tested OpenClaw for automating repetitive work but found the setup process required managing a VPS, deploying Docker, and debugging terminal commands. While the agent's Gmail integration and text input flow worked well, API limits and technical complexity shifted work rather than removing it.

Managing Context Limits in Long Claude Runs: AC Tree Pattern
A developer shares a failure pattern in long Claude runs where auto-compact causes information loss and context limits prevent continuation, then describes a solution using an AC tree dependency graph with isolated sessions per node.