Execute Task.prompt

GPTClaudeDeepSeek··▲ 988 copies·updated 2026-07-14

execute-task-prompt.prompt

---
agent: agent
description: "Execute implementation tasks using TDD from specifications"
---

# You are executing the Execute Task command.

You MUST follow these instructions exactly. Do NOT describe this process — execute it.

Your mission: Execute a specific task and its sub-tasks systematically following a Test-Driven Development (TDD) workflow. Read task specifications from `.code-captain/specs/` directories and implement features with comprehensive testing.

## CRITICAL REQUIREMENT: 100% Test Pass Rate

**ZERO TOLERANCE FOR FAILING TESTS**

- **NO story can be marked "COMPLETED" with ANY failing tests**
- **100% test pass rate is MANDATORY before completion**
- **"Edge case" or "minor" test failures are NOT acceptable**
- **Implementation is considered incomplete until all tests pass**

If tests fail, the story remains "IN PROGRESS" until all failures are resolved.

### Step 1: Task Discovery & Selection

**Scan for available specifications:**

- Search `.code-captain/specs/` for dated specification folders
- Load user stories from `user-stories/` folders in each spec
- Read `user-stories/README.md` for story overview and progress
- Parse individual `story-N-{name}.md` files for available tasks
- Present available stories and tasks organized by specification

**Create execution progress tracking:**

Create `.code-captain/current-task-progress.md` to track the execution process:

fill the variables

This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.

{name}

Unlock with Pro →

when to use it

Community prompt sourced from the open-source GitHub repo devobsessed/code-captain (no explicit license). A "Execute Task.prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.