task-execution-engine

davila7's avatarfrom davila7

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'.

⭐15.4kstars🔀1.3kforks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

The Task Execution Engine is a high-performance Claude skill designed to bridge the gap between software design and implementation. It enables autonomous agents to execute coding tasks directly from markdown-based design documents, using a structured checkbox system to track progress. By automating the implementation loop—including task retrieval, code generation, and status updates—it streamlines the development lifecycle and supports unattended, high-autonomy coding workflows.

Use Cases

  • Automated Feature Implementation: Seamlessly converting design specifications from tools like 'feature-analyzer' into functional code by executing sequential sub-tasks.
  • Unattended Batch Execution: Running complex, multi-step coding tasks without manual intervention, allowing the agent to make autonomous decisions based on existing codebase patterns.
  • Session Resumption and Recovery: Automatically picking up interrupted development work by scanning design documents for the next incomplete markdown checkbox.
  • Progress Tracking and Reporting: Maintaining a real-time, human-readable audit trail of completed, failed, or pending tasks directly within the project's documentation.
nametask-execution-engine
descriptionExecute 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'.

Feature Pipeline

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

Quick Reference

# Get next task
python3 scripts/task_manager.py next --file <design.md>

# Mark task completed
python3 scripts/task_manager.py done --file <design.md> --task "Task Title"

# Mark task failed
python3 scripts/task_manager.py fail --file <design.md> --task "Task Title" --reason "..."

# Show status
python3 scripts/task_manager.py status --file <design.md>

Task Format

Tasks are written as markdown checkboxes in the design document:

## Implementation Tasks

- [ ] **Create User model** `priority:1` `phase:model`
  - files: src/models/user.py, tests/models/test_user.py
  - [ ] User model has email and password_hash fields
  - [ ] Email validation implemented
  - [ ] Password hashing uses bcrypt

- [ ] **Implement JWT utils** `priority:2` `phase:model`
  - files: src/utils/jwt.py
  - [ ] generate_token() creates valid JWT
  - [ ] verify_token() validates JWT

- [ ] **Create auth API** `priority:3` `phase:api` `deps:Create User model,Implement JWT utils`
  - files: src/api/auth.py
  - [ ] POST /register endpoint
  - [ ] 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:

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

Failed task:

- [x] **Create User model** `priority:1` `phase:model` ❌
  - files: src/models/user.py
  - [ ] User model has email field
  - 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]