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-code

Installs 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:

  1. Continuity ledger - Current session state (what's done overall)
  2. The plan - Overall implementation plan with all phases
  3. Your specific task - What you need to implement
  4. Previous task handoff (if any) - Context from the last completed task
  5. 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
1bobmatnyc avatarapi-documentationbobmatnyc/claude-mpm-skillsBest practices for documenting APIs and code interfaces, eliminating redundant documentation guidance per agent.389skills.sh installs
2davila7 avatardspydavila7/claude-code-templatesBuild complex AI systems with declarative programming, optimize prompts automatically, create modular RAG systems and agents with DSPy - Stanford NLP's framewor376skills.sh installs
3denoland avatardeno-sandboxdenoland/skillsUse when building features that execute untrusted user code, AI-generated code, or need isolated code execution environments. Covers the @deno/sandbox SDK.365skills.sh installs
4davila7 avatarlangsmith-observabilitydavila7/claude-code-templatesLLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring p357skills.sh installs
5levnikolaevich avatarln-510-quality-coordinatorlevnikolaevich/claude-code-skillsUse when coordinating story quality evaluation with mandatory research, worker summaries, agent review, regression evidence, and bounded refinement.357skills.sh installs
6davila7 avatarcodexdavila7/claude-code-templatesUse when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Uses GPT-5.2356skills.sh installs