Task Execution Engine

Execute tasks from design docs with automated progress tracking

✨ The solution you've been looking for

Verified

Tested and verified by our team

16036 Stars

Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-design-assistant output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.

task-management implementation automation markdown feature-pipeline development cli productivity

Repository

See It In Action

Interactive preview & real-world examples

Live Demo

AI Conversation Simulator

See how users interact with this skill

User Prompt

start implementation from docs/designs/user-auth.md

Skill Processing

Analyzing request...

Agent Response

Automated execution of all implementation tasks with progress tracking and status updates

Quick Start (3 Steps)

Get up and running in minutes

Install

claude-code skill install task-execution-engine

claude-code skill install task-execution-engine

Config

First Trigger

@task-execution-engine help

Commands

Command	Description	Required Args
@task-execution-engine feature-implementation-from-design	Execute a complete feature implementation following a design document with task dependencies	None
@task-execution-engine resume-interrupted-work	Continue implementation after interruption or failure, picking up from last completed task	None
@task-execution-engine batch-task-execution	Execute multiple related implementation tasks in unattended mode without manual intervention	None

Typical Use Cases

Feature Implementation from Design

Execute a complete feature implementation following a design document with task dependencies

Resume Interrupted Work

Continue implementation after interruption or failure, picking up from last completed task

Batch Task Execution

Execute multiple related implementation tasks in unattended mode without manual intervention

Overview

Feature Pipeline

Execute implementation tasks directly from design documents. Tasks are managed as markdown checkboxes - no separate session files needed.

Quick Reference

 1# Get next task
 2python3 scripts/task_manager.py next --file <design.md>
 3
 4# Mark task completed
 5python3 scripts/task_manager.py done --file <design.md> --task "Task Title"
 6
 7# Mark task failed
 8python3 scripts/task_manager.py fail --file <design.md> --task "Task Title" --reason "..."
 9
10# Show status
11python3 scripts/task_manager.py status --file <design.md>

Task Format

Tasks are written as markdown checkboxes in the design document:

 1## Implementation Tasks
 2
 3- [ ] **Create User model** `priority:1` `phase:model`
 4  - files: src/models/user.py, tests/models/test_user.py
 5  - [ ] User model has email and password_hash fields
 6  - [ ] Email validation implemented
 7  - [ ] Password hashing uses bcrypt
 8
 9- [ ] **Implement JWT utils** `priority:2` `phase:model`
10  - files: src/utils/jwt.py
11  - [ ] generate_token() creates valid JWT
12  - [ ] verify_token() validates JWT
13
14- [ ] **Create auth API** `priority:3` `phase:api` `deps:Create User model,Implement JWT utils`
15  - files: src/api/auth.py
16  - [ ] POST /register endpoint
17  - [ ] POST /login endpoint

See references/task-format.md for full format specification.

Execution Loop

LOOP until no tasks remain:
  1. GET next task (task_manager.py next)
  2. READ task details (files, criteria)
  3. IMPLEMENT the task
  4. VERIFY acceptance criteria
  5. UPDATE status (task_manager.py done/fail)
  6. CONTINUE

Unattended Mode Rules

NO stopping for questions
NO asking for clarification
Make autonomous decisions based on codebase patterns
If blocked, mark as failed and continue

Status Updates

Completed task:

1- [x] **Create User model** `priority:1` `phase:model` ✅
2  - files: src/models/user.py
3  - [x] User model has email field
4  - [x] Password hashing implemented

Failed task:

1- [x] **Create User model** `priority:1` `phase:model` ❌
2  - files: src/models/user.py
3  - [ ] User model has email field
4  - reason: Missing database configuration

Resume / Recovery

To resume interrupted work, simply run again with the same design file:

/feature-pipeline docs/designs/xxx.md

The task manager will find the first uncompleted task and continue from there.

Integration

This skill is typically triggered after /feature-analyzer completes:

User: /feature-analyzer implement user auth

Claude: [designs feature, generates task list]
        Design saved to docs/designs/2026-01-02-user-auth.md
        Ready to start implementation?

User: Yes / 开始实现

Claude: [executes tasks via task-execution-engine]