workflow-lite-execute

Executes workflow plans by batching tasks into parallel or sequential runs with progress tracking.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps turn a workflow plan into executed work by batching tasks for parallel or sequential execution, tracking progress, optionally resuming failed tool runs, and chaining into a follow-up test/review phase.

Core Features & Use Cases

  • Multi-mode input: Accepts an in-memory execution context, a plain task description, or a plan file whose content may include task IDs and loaded task artifacts.
  • Dependency-aware batching: Groups independent tasks into per-executor parallel calls, then runs dependent tasks in a dependency-respecting sequence with ready-set parallelization.
  • Tool routing and resumption: Selects executors per task (agent, codex, or gemini) using overrides and complexity-based fallback, and supports resuming CLI runs via deterministic IDs on failure/timeout.
  • Optional post-execution code review: Runs code quality review via Agent, Codex review mode, or Gemini review mode, or skips cleanly when configured.
  • Handoff to test review: Chains execution results into workflow-lite-test-review with a constructed testReviewContext.

Quick Start

Call the skill with the flag --in-memory when workflow-lite-plan approval already produced an executionContext, or call it with a task description like Add unit tests for auth module to generate an execution plan and start execution.

Frequently Asked Questions about workflow-lite-execute

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

FAQPage Schema
How do I execute workflow plans with dependency-aware parallel batching?

Dependency-aware execution groups independent tasks into per-executor parallel calls, then runs dependent tasks in a ready-set sequence. This workflow batching respects task dependency graphs while parallelizing independent items for faster completion.

Can I resume task execution after a CLI timeout or failure?

Yes, you can resume failed CLI runs using deterministic resumption IDs. This mechanism tracks progress per task, allowing execution to recover from timeouts or failures without restarting the entire workflow plan.

How do I route workflow tasks to different executors like agent, codex, or gemini?

Tool routing selects executors per task using explicit overrides and complexity-based fallback. It automatically assigns tasks to agent, codex, or gemini executors based on task requirements and configured routing rules.

What is the best way to chain task execution into a code review and test workflow?

The best way is to chain execution results directly into a test review phase. After batched execution completes, it constructs a test review context and hands off to the test review workflow for validation.

Do I need a plan file to start task execution, or can I use a plain task description?

You do not need a plan file. The execution workflow supports multi-mode input, accepting an in-memory execution context, a plain task description, or a plan file containing task IDs and loaded task artifacts.

How does dependency graph batching handle sequential and parallel task execution?

Dependency graph batching groups independent tasks into parallel executor calls while running dependent tasks in a dependency-respecting sequence. It uses ready-set parallelization to maximize throughput without violating task dependencies.