workflow-executor

Workflow automation with per-step validation orchestrates Markdown-defined workflows through a dedicated executor, applying sandbox isolation and validation state tracking to each step. This ensures deterministic execution and real-time progress feedback across your entire pipeline.

Yes. The workflow executor runs CLI-based workflows from Markdown definitions with per-step Task invocations, named-input sandboxes for isolation, and input/output routing between steps. Each step executes in its own sandbox with validation enforcement.

Validation-driven completion tracks field presence, detects deprecated syntax, and maintains per-step validation state throughout execution. Real-time TUI streaming visualizes progress and tool feedback, enabling you to catch issues at each step before proceeding.

Define workflows in workflows/*.md using the skills-first architecture, then execute via CLI with `looplia run [workflow-name] --file [path]`. The executor handles step-by-step orchestration, sandbox setup, and per-step validation automatically.

Yes. The executor supports named-input sandboxes and explicit input/output routing, allowing outputs from one step to feed into subsequent steps while maintaining sandbox isolation and validation state across the workflow.

The executor enforces field presence validation, detects and rejects deprecated syntax, and applies validation state tracking across all steps. Violations surface during execution, preventing progression until requirements are met.