/ct-task-executor

name: ct-task-executor
description: General implementation task execution for completing assigned CLEO tasks by following instructions and producing concrete deliverables. Handles coding, configuration, documentation work with quality verification against acceptance criteria and progress reporting. Use when executing implementation tasks, completing assigned work, or producing task deliverables. Triggers on implementation tasks, general execution needs, or task completion work.
version: 2.8.8
protocol: implementation
adrRefs:
  - ADR-070
  - ADR-062
dependencies: []
sharedResources:
  - subagent-protocol-base
  - task-system-integration
compatibility:
  - claude-code
  - cursor
  - windsurf
  - gemini-cli
license: MIT
metadata:
  version: 2.8.8
  tier: core
  install: harness
  covers:
    - packages/cleo/src/cli/commands/verify.ts
    - packages/cleo/src/cli/commands/complete.ts
    - packages/cleo/src/cli/commands/start.ts
    - packages/cleo/src/cli/commands/claim.ts
    - packages/core/src/doctor/container-reaper.ts
    - packages/core/src/validation/protocols/cant/implementation.cant
    - packages/core/src/validation/protocols/protocols-markdown/implementation.md
  loomStage: implementation
  lastReviewed: 2026-10-26
  stability: stable

Task Executor Context Injection

Trustworthy project knowledge

After confirming the assigned worktree, orient with briefing/focus. Check current coverage and sourced authority before acting on retrieved guidance. `UNKNOWN` impact is incomplete assessment; `NONE` is no detected impact in assessed static coverage, never proof of no runtime callers. Resolve ambiguous symbols explicitly. Preserve historical handoffs and follow sourced corrections separately.

Consume repair findings as a matrix of scope, evidence, responsibility, operation, prerequisites, verification, and recovery. The foreground calling agent supplies sourced resolutions; repair never requires a background model. Escalate unresolved owner decisions, reject stale proposals, verify postconditions, and record useful incident learning with project/revision evidence. A failed diagnostic is not clean. Provider reference delivery must be verified or embedded self-contained; static instruction checks do not establish live Codex, Claude, or Kimi behavior.

**Protocol**: @src/protocols/implementation.md **Type**: Context Injection (cleo-subagent) **Version**: 2.0.0

---

Purpose

Context injection for implementation tasks spawned via cleo-subagent. Provides domain expertise for completing assigned CLEO tasks by following their instructions and deliverables to produce concrete outputs.

---

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

---

Parameters (Orchestrator-Provided)

| 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 for output | Yes | | `{{DATE}}` | Current date (YYYY-MM-DD) | Yes | | `{{EPIC_ID}}` | Parent epic identifier | No | | `{{SESSION_ID}}` | Session identifier | No | | `{{DEPENDS_LIST}}` | Dependencies completed | No | | `{{MANIFEST_SUMMARIES}}` | Context from previous agents | No | | `{{TOPICS_JSON}}` | JSON array of categorization tags | Yes |

---

Task System Integration

@skills/_shared/task-system-integration.md

Execution Sequence

1. Read task: `{{TASK_SHOW_CMD}} {{TASK_ID}}` 2. Focus already set by orchestrator (set if working standalone) 3. Execute instructions (see Methodology below) 4. Verify deliverables against acceptance criteria 5. Record output: `cleo docs add {{TASK_ID}} --content - --type note --slug {{TOPIC_SLUG}}` 6. Record the manifest entry: `cleo manifest append --task {{TASK_ID}} --type implementation --content "<one-paragraph summary>"` 7. Complete task: `{{TASK_COMPLETE_CMD}} {{TASK_ID}}` 8. Return summary message

---

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

Throwaway Containers

A database or service started for a test run must not outlive it. A `docker run` without `--rm` leaves an anonymous volume behind on every run; on 2026-10-10 that came to 475 volumes and 52 GB.

• One-shot: `docker run --rm --label cleo.task=T#### --label cleo.ttl=4h postgres:17 …`
• Reused across runs: a named volume (`-v t####-pgdata:/var/lib/postgresql/data`) plus the same two labels, and stop the container when the task ends.
• `cleo doctor system` reports long-running database containers and dangling volumes. `cleo doctor system --repair` lists, as a dry run, the STOPPED `cleo.ttl` containers that stopped longer ago than their ttl (or were created that long ago and never started), and the anonymous dangling volumes (including ones left by non-CLEO containers). `--repair --apply` removes only those. It never removes a running container: one running past its ttl since its last start is reported for you to stop. It never touches an unlabelled container or a named volume. R