Task Executor

General implementation skill for completing CLEO tasks

Task Executor

The Task Executor skill provides context injection for implementation tasks, enabling completion of coding, configuration, and documentation work.

Overview

Property	Value
Skill ID	ct-task-executor
Tier	2 (Execution)
Protocol	implementation
Tags	execution, implementation

Capabilities

1. Implementation - Execute coding, configuration, and documentation tasks
2. Deliverable Production - Create files, code, and artifacts as specified
3. Quality Verification - Validate work against acceptance criteria
4. Progress Reporting - Document completion via subagent protocol

When to Use

The dispatch algorithm selects ct-task-executor for:

• Tasks with keywords: implement, build, execute, create
• Tasks labeled: implementation
• Default fallback when no other skill matches

Parameters

Parameter	Description	Required
{{TASK_ID}}	Current task identifier	Yes
{{TASK_NAME}}	Human-readable task name	Yes
{{TASK_INSTRUCTIONS}}	Specific execution instructions	Yes
{{DELIVERABLES_LIST}}	Expected outputs/artifacts	Yes
{{ACCEPTANCE_CRITERIA}}	Completion verification criteria	Yes
{{TOPIC_SLUG}}	URL-safe topic name	Yes

Execution Flow

1. Read task details
   └─→ cleo show {{TASK_ID}}

2. Focus already set by orchestrator
   └─→ (set if working standalone)

3. Execute instructions
   └─→ Follow methodology below

4. Verify deliverables
   └─→ Check against acceptance criteria

5. Write output
   └─→ {{OUTPUT_DIR}}/{{DATE}}_{{TOPIC_SLUG}}.md

6. Append manifest
   └─→ {{MANIFEST_PATH}}

7. Complete task
   └─→ cleo complete {{TASK_ID}}

8. Return summary
   └─→ "Implementation complete. See MANIFEST.jsonl for summary."

Methodology

Pre-Execution

1. Read task details - Understand full context from task system
2. Review dependencies - Check manifest summaries from previous agents
3. Identify deliverables - Know exactly what to produce
4. Understand acceptance criteria - Know how success is measured

Execution

1. Follow instructions - Execute {{TASK_INSTRUCTIONS}} step by step
2. Produce deliverables - Create each item in {{DELIVERABLES_LIST}}
3. Document as you go - Track progress for output file
4. Handle blockers - Report if unable to proceed

Post-Execution

1. Verify against criteria - Check each acceptance criterion
2. Document completion - Write detailed output file
3. Update manifest - Append summary entry
4. Complete task - Mark task done in task system

Output Format

Output File

# {{TASK_NAME}}

## Summary

{{2-3 sentence overview of what was accomplished}}

## Deliverables

### {{Deliverable 1}}

{{Description of what was created/modified}}

**Files affected:**
- {{file path 1}}
- {{file path 2}}

## Acceptance Criteria Verification

| Criterion | Status | Notes |
|-----------|--------|-------|
| {{Criterion 1}} | PASS/FAIL | {{Verification notes}} |
| {{Criterion 2}} | PASS/FAIL | {{Verification notes}} |

## Implementation Notes

{{Technical details, decisions made, edge cases handled}}

Manifest Entry

{"id":"{{TOPIC_SLUG}}-{{DATE}}","file":"{{DATE}}_{{TOPIC_SLUG}}.md","title":"{{TASK_NAME}}","date":"{{DATE}}","status":"complete","agent_type":"implementation","topics":["implementation"],"key_findings":["Completed: deliverable 1","Completed: deliverable 2","All acceptance criteria passed"],"actionable":false,"needs_followup":[],"linked_tasks":["{{TASK_ID}}"]}

Error Handling

Partial Completion

If all deliverables cannot be produced:

1. Complete what is possible
2. Document partial progress in output file
3. Set manifest "status": "partial"
4. Add blocking items to needs_followup

Blocked Execution

If work cannot proceed:

1. Document blocking reason in output file
2. Set manifest "status": "blocked"
3. Do NOT complete task
4. Return: “Implementation blocked. See MANIFEST.jsonl for blocker details.”

Related Skills

• Epic Architect - Decomposes work into executable tasks
• Spec Writer - Defines requirements before implementation
• Validator - Verifies implementation meets spec