task-execution-engine
Executes coding tasks tracked via markdown checkboxes in design documents.
Install
mkdir -p .claude/skills/task-execution-engine && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/759" && unzip -o skill.zip -d .claude/skills/task-execution-engine && rm skill.zipInstalls to .claude/skills/task-execution-engine
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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'.Key capabilities
- →Parse markdown files for tasks
- →Track task completion via checkboxes
- →Execute tasks sequentially
- →Resume interrupted work sessions
- →Handle task failures with reasons
How it works
It parses markdown checkboxes in a design document and cycles through them, updating the file status as tasks are completed or failed.
Inputs & outputs
When to use task-execution-engine
- →Implementing features from a design doc
- →Resuming interrupted coding sessions
- →Executing batch programming tasks
About this skill
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]
When not to use it
- →When tasks are not defined in markdown format
- →When complex state management requires external databases
Prerequisites
Limitations
- →Requires specific markdown task format
- →Limited to sequential task execution
How it compares
It manages task state directly within the markdown file without requiring external session files or databases.
Compared to similar skills
task-execution-engine side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| task-execution-engine (this skill) | 3 | 7mo | Review | Beginner |
| workflow-linear-tracking | 0 | 5mo | Review | Beginner |
| today | 0 | 6mo | No flags | Beginner |
| scan-deck | 0 | 1mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by davila7
View all by davila7 →You might also like
workflow-linear-tracking
riordanpawley
Issue Tracking Skill (`linear-cli` backend)
today
kv0906
Guided daily workflow orchestrator. Multi-phase process (standup, team sync, review, focus, wrap-up). Use when user says "today", "start my day", or "daily workflow".
scan-deck
zauberzeug
Browse the deck — supportive triage view, filtered queues, kanban board, JSON dump, decision Q&A. Read-only by default. AUTO-INVOKE on "what's open", "show me the deck", "kanban view", or "decisions to make" — and ALWAYS before Skill(create-card) to dedup against existing titles.
github-project-management
ruvnet
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
create-plans
glittercowboy
Create hierarchical project plans optimized for solo agentic development. Use when planning projects, phases, or tasks that Claude will execute. Produces Claude-executable plans with verification criteria, not enterprise documentation. Handles briefs, roadmaps, phase plans, and context handoffs.
phasing
WellApp-ai
Group slices into risk-optimized phases with timeline generation