task_complete

Task Complete Command - Production-Ready Feature Implementation

YOUR ROLE: ORCHESTRATOR ONLY

YOU ARE THE ORCHESTRATOR. You must NOT write any code, read files for implementation, or make any edits yourself. Your ONLY job is to call the Task tool to spawn specialized subagents in sequence. If you find yourself writing code or editing files, STOP — you are doing it wrong. Delegate everything.

---

SETUP

Run this bash command to create the task directory:

TIMESTAMP=$(date +"%Y-%m-%d-%H-%M-%S") && mkdir -p "./claude-tasks/${TIMESTAMP}_task" && echo "./claude-tasks/${TIMESTAMP}_task"

From the output, derive a 2-4 word slug from the task description (e.g. invoice-redesign, auth-fixes, timer-system) and rename:

mv "./claude-tasks/${TIMESTAMP}_task" "./claude-tasks/${TIMESTAMP}_{SLUG}"

Set TASK_DIRECTORY to the final path. Save the task description:

echo "$ARGUMENTS" > "$TASK_DIRECTORY/TASK.md"

---

STEP 1 — CALL Task tool: tc-context-gatherer

IMMEDIATELY call the Task tool with these parameters. Do NOT skip this.

• subagent_type: tc-context-gatherer
• description: "Gather project context"
• prompt:

  Task directory: {TASK_DIRECTORY}
  Task: {TASK_DESCRIPTION}
  
  Analyze the complete codebase. Save comprehensive context to {TASK_DIRECTORY}/context.md.
  Capture baseline lint and build metrics. Save to {TASK_DIRECTORY}/validation-tracking.json with this shape:
  { "baseline": { "lint_errors": N, "build_success": true/false, "timestamp": "..." }, "current": null, "validation_passed": false }
  

BLOCKING GATE: Do NOT proceed to Step 2 until the Task tool call returns.

---

STEP 2 — CALL Task tool: tc-task-planner

IMMEDIATELY call the Task tool with these parameters.

• subagent_type: tc-task-planner
• description: "Create implementation plan"
• prompt:

  Task directory: {TASK_DIRECTORY}
  Task: {TASK_DESCRIPTION}
  
  Read {TASK_DIRECTORY}/context.md. Create a detailed, file-level implementation plan.
  Save to {TASK_DIRECTORY}/plan.md.