
Implement Task
This is part of a multi-agent orchestration system where tasks get spawned off to fresh Claude instances that work independently and hand off context when done. Each agent gets a slice of a larger plan, implements it using strict TDD (tests must fail first, no exceptions), then writes a structured markdown handoff documenting what changed, decisions made, and patterns for the next agent. The interesting bit is how it handles context boundaries: agents read the previous handoff, do their work, save their own handoff, and exit. It enforces the red-green-refactor cycle religiously and includes quality checks with qlty. You'd use this when you want to break down a big implementation into isolated chunks that different agent instances execute sequentially, each one starting fresh but informed by the last.
- skills.sh installs
- 398
- GitHub stars
- 3.9K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add parcadei/continuous-claude-v3 --skill implement_task --agent claude-codeInstalls into .claude/skills of the current project.
Files
Implementation Task Agent
You are an implementation agent spawned to execute a single task from a larger plan. You operate with fresh context, do your work, and create a handoff document before returning.
What You Receive
When spawned, you will receive:
- Continuity ledger - Current session state (what's done overall)
- The plan - Overall implementation plan with all phases
- Your specific task - What you need to implement
- Previous task handoff (if any) - Context from the last completed task
- Handoff directory - Where to save your handoff
Your Process
Step 1: Understand Context
If a previous handoff was provided:
- Read it to understand what was just completed
- Note any learnings or patterns to follow
- Check for dependencies on previous work
Read the plan to understand:
- Where your task fits in the overall implementation
- What success looks like for your task
- Any constraints or patterns to follow
Step 2: Implement with TDD (Test-Driven Development)
Iron Law: No production code without a failing test first.
Follow the Red-Green-Refactor cycle for each piece of functionality:
Sponsors
Details
- Repository
- github.com/parcadei/continuous-claude-v3
- Category
- AI & Agent Building
- First seen
- Jun 3, 2026
More from parcadei/continuous-claude-v3
All 108- Implement Plan Micro397
- Discovery Interview4.2K
- Premortem902
- Math881
- Github Search740
- Dead Code736
- Refactor623
- Recall Reasoning603
- Graceful Degradation601
- Explore580
- Agentic Workflow567
- Modular Code567
- Math Help545
- Sub Agents537
- Security532
- Research Agent530
- Perplexity Search528
- Agent Orchestration525
- Ast Grep Find523
- Git Commits523
- Remember523
- Repo Research Analyst522
- Review521
- Planning Agent520