Implementation

What it does and when to use it

Execute implementation tasks from task documents following TDD workflow, phase-by-phase execution, and real-time progress tracking. USE WHEN implement, execute tasks, run tasks, start implementation, build feature, execute implementation, code the feature.

How it works

1. Customization
2. Prerequisites
3. Workflow Routing
4. Task Discovery
5. Execution Model
6. Output
7. Examples

---
name: Implementation
description: Execute implementation tasks from task documents following TDD workflow, phase-by-phase execution, and real-time progress tracking. USE WHEN implement, execute tasks, run tasks, start implementation, build feature, execute implementation, code the feature.
---

# Implementation

Execute tasks from `tasks.md` following TDD workflow with phase-by-phase execution, progress tracking, and completion validation.

## Customization

**Before executing, check for user customizations at:**
`~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Implementation/`

If this directory exists, load and apply any PREFERENCES.md configurations. If not, proceed with defaults.

## Prerequisites

1. LifeOS must be installed. Check `~/.claude/LIFEOS/VERSION`.
2. Foundation must exist at `/directive/foundation.md`.
3. Tasks must exist in `specs/` directory.

## Workflow Routing

| Workflow | Trigger | File |
|----------|---------|------|
| **ExecuteTasks** | Any invocation | `Workflows/ExecuteTasks.md` |

## Task Discovery

Scans `specs/` for folders containing `tasks.md`. If multiple found, asks user which to execute.

## Execution Model

- **Phase-by-phase**: Setup -> Tests (TDD) -> Core -> Integration -> Polish
- **TDD**: Tests MUST fail first (red), then pass after implementation (green)
- **Progress**: Updates checkboxes in `tasks.md` after each completed task
- **Errors**: Halts on sequential task failure; continues on parallel `[P]` failure

## Output

Updates `tasks.md` in-place with completion checkboxes. Changes status to "Completed" when done.

## Examples

**Example 1: Execute implementation**
```
User: "/buddy:implement"
-> Discovers specs/20260402-user-authentication/tasks.md
-> Reads all design documents (spec, plan, tasks, data-model, etc.)
-> Executes Phase 3.1 Setup tasks
-> Executes Phase 3.2 Tests (expects failures - TDD red)
-> Executes Phase 3.3 Core (tests should pass - TDD green)
-> Executes Phase 3.4 Integration, Phase 3.5 Polish
-> Updates tasks.md checkboxes throughout
-> Reports completion summary
```

Versions

Database snapshot: 13.11.2026 · package version 3c3d7fd7657a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 100spec-driven-implementation
  Execute spec-driven implementation — auto-detects Quick (plan.md) or Full (tasks.md) mode and runs step-by-step with verification. Use when implementing a planned feature or running TDD tasks.
• 90implement
  Execute an implementation plan step by step with verification checkpoints and progress tracking. Use when the user asks to "implement the plan", "execute the steps", "start implementing", or has an approved plan ready to implement.
• 95execute-tdd-tasks
  Execute TDD task pairs autonomously with RED-GREEN-REFACTOR verification. Orchestrates wave-based execution with strategic parallelism, routing TDD tasks to tdd-executor agents and non-TDD tasks to standard task-executor. Use when user says "execute tdd tasks", "run tdd tasks",…
• 90rpi-implement
  Execute an approved plan from .rpi/plans phase by phase with TDD and per-phase verification. Use when user says 'implement the plan', 'start implementing', 'run the next phase', or just approved a plan.
• 90rpi-implement
  Execute an approved plan from .rpi/plans phase by phase with TDD and per-phase verification. Use when user says 'implement the plan', 'start implementing', 'run the next phase', or just approved a plan.
• 100task-execution-engine
  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'.