implement_task

Spawn an implementation agent to execute a task and generate a handoff document.

1|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/tfunk1030/vibe --skill implement-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement_task
Source: https://github.com/tfunk1030/vibe/tree/main/.claude/skills/implement_task
Command: npx skills add https://github.com/tfunk1030/vibe --skill implement-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the execution of a single, contained task by spawning an implementation agent that processes the task within a larger plan, using fresh context and producing a standardized handoff upon completion.

Core Features & Use Cases

  • Red-Green-Refactor workflow: Enforces a test-driven development cycle for each task to ensure correctness before implementation.
  • Handoff generation: Produces a structured handoff document detailing changes, decisions, and next steps for downstream tasks.
  • Context-driven execution: Consumes continuity ledger, plan, and task details to maintain alignment and traceability across tasks.
  • Plan-first automation: Ideal for planning-heavy environments where tasks are decomposed into clear, repeatable steps and require auditable handoffs.

Quick Start

Spawn the implementation task agent with the provided plan, continuity ledger, and task details, then review the generated handoff document.

Frequently Asked Questions about implement_task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate test-driven development task execution with structured handoffs?

Automate test-driven development task execution by spawning an implementation agent that enforces Red-Green-Refactor cycles and generates a standardized handoff document. The agent consumes your plan and continuity ledger to process each task with fresh context, ensuring traceable downstream transitions.

What is a standardized handoff document in a planning-heavy software workflow?

A standardized handoff document in a planning-heavy workflow details all code changes, design decisions, and next steps for downstream tasks. It is produced automatically by the implementation agent upon completing a single decomposed task, maintaining alignment across the broader plan.

How do I enforce Red-Green-Refactor cycles for each decomposed task in my plan?

Enforce Red-Green-Refactor cycles for decomposed tasks by spawning an implementation agent that validates behavior with failing tests first. The agent strictly follows this test-driven development sequence before completing the task and producing the final handoff.

Do I need a continuity ledger and plan to run a focused task execution agent?

You need a continuity ledger and plan to run a focused task execution agent because it consumes these inputs to maintain alignment and traceability. Providing decomposed task details alongside these documents ensures the agent processes the work with proper context.

What's the best way to maintain traceability across decomposed software tasks?

Maintain traceability across decomposed software tasks by consuming a continuity ledger and plan to drive context-driven execution. The implementation agent uses these inputs to process each task and outputs a consistent handoff document, linking every change to the larger plan.

Can I use task-execution automation for single contained tasks instead of full projects?

Task-execution automation is designed specifically for single contained tasks rather than full projects. It spawns an implementation agent to process one decomposed step within a larger plan, validating behavior with failing tests before delivering a structured handoff.