Markdown agent flows (mdflow)

Tool roles, alternatives, selection tradeoffs, and compatibility caveats.

Tool roles, alternatives, selection tradeoffs, and compatibility caveats.

Markdown agent flows (mdflow)

John uses: mdflow (md, 597, MIT) — executable markdown prompts run against Claude, Codex, Gemini, or Copilot. The differentiators, per section 05: prompt-build-time command inlining (!`git status`), frontmatter _inputs, isolation from all ambient config/hooks/CLAUDE.md, and eval-gated evolution (md feedback → md eval → md evolve, proposal-first).

Alternative What it is How it differs License
Claude Code slash commands & skills (built-in) Markdown files in .claude/commands and .claude/skills that become reusable parameterized agent behaviors Ships with the agent — but tied to Claude Code and inherits ambient config; mdflow's isolation and multi-engine targeting are the delta product docs
dotprompt Google's executable GenAI prompt template format (.prompt files: frontmatter + template) A file-format/spec with runtimes, aimed at app code rather than launching coding agents Apache-2.0
BAML A programming language for agents/prompts with typed inputs/outputs and tests Full typed DSL + toolchain where mdflow stays plain markdown; heavier but testable Apache-2.0
fabric patterns Markdown prompt 'patterns' executed via the fabric CLI against any model Same 'prompt as a file you run' idea, without engine flags, context inlining, or eval-gated evolution MIT
llm templates YAML templates with params for the llm CLI Lightweight parameterized prompts; no agent-loop execution or tool use Apache-2.0

Pick this if…

  • Claude Code commands/skills — you're all-in on one agent; you give up mdflow's isolation and multi-engine targeting.
  • fabric — you want "prompt as a runnable file" without engine flags or context inlining.
  • llm templates — lightweight parameterized prompts, no agent loop.
  • BAML — you want types and tests around prompts and will trade markdown simplicity for it.
  • dotprompt — you're standardizing prompt files inside application code, not agent launches.

Source references