wf-player

Execute DAG-ordered workflow templates with parallel batches and resumable checkpoints.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/tcytan/tecton --skill wf-player
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-player
Source: https://github.com/tcytan/tecton/tree/main/.claude/skills/wf-player
Command: npx skills add https://github.com/tcytan/tecton --skill wf-player

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

wf-player eliminates the hassle of manually coordinating multi-step workflows by automatically loading a workflow template, executing its DAG nodes in the correct order, and persisting progress so you can resume after pauses or interruptions.

Core Features & Use Cases

  • Template-driven execution (DAG + batches): Executes workflow nodes according to a DAG-derived topological order, including parallel node batches.
  • Context binding & validation: Binds template-required variables from --context, validates required inputs, and supports dry-run planning.
  • Resumable sessions with checkpoints: Persists session-state.json and checkpoint snapshots, supports --resume <session-id>, and can pause at checkpoints for user review.

Quick Start

Run your saved template by providing its slug and context, then let wf-player execute the workflow with checkpoints: invoke Skill(wf-player) with the arguments "<template-slug> --context goal='...'".

Frequently Asked Questions about wf-player

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a workflow template with resumable checkpoints for multi-step orchestration?

DAG execution with parallel batches works by deriving a topological order from the workflow template's JSON definition. It then runs nodes sequentially or in parallel batches, invoking node executors deterministically per node type.

Can I resume a paused workflow session after an interruption?

Yes, you can validate workflow template inputs before execution using a dry-run planning mode. This checks that all required context variables from --context are properly bound and available before running any nodes.

What's the best way to coordinate multi-step agent and CLI command orchestration with persisted state?

Yes, the workflow player supports parallel node batches within its DAG execution. It resolves node argument references and runs grouped nodes in parallel batches alongside the standard topological order execution.

Why does my workflow orchestration fail when context variables are missing?

Workflow orchestration fails when context variables are missing because the system validates required inputs during context binding. You must provide all necessary variables via --context arguments before DAG execution begins.