Why is Git initialization mandatory for this skill?

Git is required to provide an audit trail of all implementation changes and to facilitate the post-task commit hooks that track exactly what each subagent modified.

What is contained in the execution evaluation report?

The report provides a summary of all task outcomes, verification verdicts based on acceptance criteria, and a list of created or modified files.

How does the skill handle implementation failures?

It uses a checkpoint system to detect orphaned or failed tasks. Users can choose to retry tasks from the last known state, skip them, or abort the process for manual investigation.

What is the prerequisite for using the execute skill?

The execute skill requires a completed task plan generated by the Tasker /plan phase and a initialized state file located in the .tasker directory.

How many tasks can be executed simultaneously?

By default, the skill is limited to 3 parallel executors to prevent orchestrator context exhaustion and ensure stability during the development process.

Tasker Execute Engine

Name: Tasker Execute Engine
Author: Dowwie

byDowwie

•

Productivity & Workflow

Executes complex development plans using coordinated subagents to implement features from spec-driven task graphs.

The Tasker Execute skill is the core implementation engine of the Tasker framework, designed to turn structured plans into production-ready code. It manages a parallel execution loop that spawns isolated subagents, each responsible for a specific node in a task dependency graph (DAG). With built-in crash recovery, Git-integrated audit trails, and automated evaluation reports, it provides a robust, fail-safe environment for agentic software development, ensuring that complex multi-file implementations remain consistent and well-documented.