Agent skill

TDD Migration Pipeline

by parcadei in parcadei/Continuous-Claude-v3

Orchestrator-only workflow for migrating/rewriting codebases with full TDD and agent delegation

MITAuto-check: notesTesting & QA

Install TDD Migration Pipeline

skills CLI
$ npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migration-pipeline -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install parcadei/Continuous-Claude-v3 tdd-migration-pipeline --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/tdd-migration-pipeline .claude/skills/tdd-migration-pipeline && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tdd-migration-pipeline
GitHub stars
3.9k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
287 words
Files
1
Skills in repo
141
Repo updated
First seen
Licence
MIT

At a glance

Orchestrator-only workflow for migrating/rewriting codebases with full TDD and agent delegation

  • Works in 6 steps: SPEC → FAILING TESTS → ADVERSARIAL (x3 iterations) → …
  • Tasks that involve Test-driven development
  • SKILL.md covers When to Use, Core Principles, Your Constraints and Pipeline Phases, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

TDD Migration Pipeline is an agent skill from parcadei/Continuous-Claude-v3. Orchestrator-only workflow for migrating/rewriting codebases with full TDD and agent delegation

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test-driven development. The repository describes itself as: Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context pollution. Agent orchestration with isolated context windows. The licence is MIT.

When your agent uses it

  • Tasks that involve Test-driven development

Example prompts

  • “/tdd-migration-pipeline”

Requirements

  • Pre-approved tools (allowed-tools): Task, TodoWrite, Read, Bash

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. SPEC
  2. FAILING TESTS
  3. ADVERSARIAL (x3 iterations)
  4. PHASED PLAN
  5. BUILD LOOP (per phase)
  6. INTEGRATION VALIDATION

What it can do on your machine

Read from SKILL.md and the folder at commit d07ff4b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Task
    • TodoWrite
    • Read
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

TDD Migration Pipeline loads about 1.4k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 287 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Task, TodoWrite, Read, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from parcadei/Continuous-Claude-v3 at commit d07ff4b, republished under its MIT licence (© parcadei). 287 words, ~1,448 tokens.

Download SKILL.mdSave it as .claude/skills/tdd-migration-pipeline/SKILL.md (or your agent's skills folder).
name
tdd-migration-pipeline
description
Orchestrator-only workflow for migrating/rewriting codebases with full TDD and agent delegation
allowed-tools
Task, TodoWrite, Read, Bash

TDD Migration Pipeline

Orchestrator-only workflow for migrating or rewriting codebases. You do NOT read files, write code, or validate anything yourself. You only instruct agents and pipe context (paths, not contents).

When to Use

  • Migrating codebase from one language/framework to another
  • Rewriting a system with TDD guarantees
  • Large-scale refactoring with behavioral contracts
  • When you want zero context growth in the orchestrator

Core Principles

  1. ZERO orchestrator execution - only instruct and pipe context
  2. All work done by agents - you never read/write/validate
  3. Context window stays flat - pass paths, not contents
  4. New code in separate directory - never modify source

Your Constraints

  • Never say "let me read..." or "looking at..."
  • Only say "Agent X: do Y with Z"
  • Your context should NOT grow during execution
  • All agents must use qlty and tldr skills

Pipeline Phases

Phase 1: SPEC
Instruct spec-agent (use scout or architect):
- Analyze {source_path} using tldr-skill
- Output: spec.md with behavioral contracts, types, edge cases

Agent prompt template:

Analyze the codebase at {source_path} using tldr commands (tldr structure, tldr extract, tldr calls).
Create spec.md with:
- All behavioral contracts (what each function/class promises)
- Input/output types
- Edge cases and invariants
- Dependencies between components
Write to: {target_dir}/spec.md
Phase 2: FAILING TESTS
Instruct test-agent (use arbiter):
- Read spec.md
- Write failing tests in {target_dir}/tests/
- Tests should define expected behavior before implementation

Instruct review-agent (use critic):
- Validate tests cover spec completely
- No gaps in behavioral coverage
Phase 3: ADVERSARIAL (x3 iterations)
Instruct premortem-agent (use premortem skill):
- Review spec + tests
- Identify failure modes, race conditions, edge cases
- DO NOT ASK - just add mitigations directly to spec
- Run 3 passes with fresh perspective each time

Key: Each pass should find NEW issues, not repeat previous ones.

Phase 4: PHASED PLAN
Instruct planner-agent (use architect or plan-agent):
- Input: spec.md + tests + mitigations
- Output: phased-plan.yaml
- Requirements:
  - Dependency-ordered phases
  - Each phase = one testable unit
  - Clear inputs/outputs per phase
Phase 5: BUILD LOOP (per phase)
For each phase in phased-plan.yaml:

  Instruct builder-agent (use kraken or spark):
  - Write code to pass tests for this phase
  - Use qlty for quality checks
  - Run tests after each change

  Instruct review-agent (use critic or judge):
  - Validate implementation matches spec
  - Check for regressions in previous phases
  - Verify no breaking changes
Phase 6: INTEGRATION VALIDATION
Instruct integration-agent (use atlas or validator):
- Use tldr to diff against {reference_repo}
- Check for:
  - No race conditions
  - No hangs or deadlocks
  - No breaking changes vs original
  - All behavioral contracts preserved
- Output: validation-report.md

Invocation

When invoking this workflow, specify:

yaml
SOURCE: {path to source code}
TARGET_DIR: {new folder for migrated code}
TARGET_LANG: {typescript|python|go|rust|etc}
REFERENCE_REPO: {url or path for final diff comparison}
SKILLS: [tldr-code, qlty-check, {domain-specific}]

Agent Mapping

PhaseAgent TypeSubagent
Specresearchscout or architect
Testsvalidatearbiter
Reviewreviewcritic or judge
Premortemreviewpremortem skill
Planplanarchitect or plan-agent
Buildimplementkraken (large) or spark (small)
Integrationvalidateatlas or validator

Example Orchestration

# Phase 1
Task(scout): "Analyze /src/old-system using tldr structure and tldr extract.
              Create spec.md at /migration/spec.md with all behavioral contracts."

# Phase 2
Task(arbiter): "Read /migration/spec.md. Write failing tests to /migration/tests/
               that define expected behavior."

Task(critic): "Review /migration/spec.md vs /migration/tests/.
              Report any behavioral gaps."

# Phase 3 (x3)
Task(premortem): "Review /migration/spec.md and /migration/tests/.
                 Identify failure modes. Add mitigations directly to spec. Pass 1/3."
[repeat with "Pass 2/3", "Pass 3/3"]

# Phase 4
Task(architect): "From /migration/spec.md and /migration/tests/,
                 create /migration/phased-plan.yaml with dependency-ordered phases."

# Phase 5 (loop)
Task(kraken): "Implement phase 1 from /migration/phased-plan.yaml.
              Code goes in /migration/src/. Run tests after."

Task(critic): "Review /migration/src/ against /migration/spec.md.
              Check for spec compliance and regressions."
[repeat for each phase]

# Phase 6
Task(atlas): "Run full integration tests on /migration/src/.
             Use tldr to diff against /src/old-system.
             Output /migration/validation-report.md."

Anti-Patterns (DO NOT)

  • Reading files into your context ("let me check the code...")
  • Writing code directly ("I'll implement this function...")
  • Validating anything yourself ("looking at the tests, I see...")
  • Modifying the source directory
  • Skipping the adversarial phase
  • Running build without tests first

Success Criteria

  • All tests pass
  • qlty reports clean
  • tldr diff shows no breaking changes
  • No race conditions or hangs
  • validation-report.md confirms behavioral equivalence

© parcadei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/tdd-migration-pipeline of parcadei/Continuous-Claude-v3.

Open the folder on GitHubat commit d07ff4b

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in parcadei/Continuous-Claude-v3, which our catalogue first saw on October 7, 2026.

Compare with similar skills

TDD Migration Pipeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

TDD Migration Pipeline compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
TDD Migration Pipeline this skillparcadei/Continuous-Claude-v33.9k1 repos~1.4kAutomated safety check: NotesMIT
TDDpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph11211 repos~2.4kAutomated safety check: PassNone
TDDsanity-io/sanity6.4k20 repos~1kAutomated safety check: PassMIT
Test Driven Developmentfarm-fe/farm5.6k51 repos~2.5kAutomated safety check: PassMIT
Tapd Story PipelineTencentBlueKing/bk-bcs840—~2.6kAutomated safety check: PassCustom licence

Similar skills

  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed
  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed
  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Testing & QAAuto-check passed
  • A skill your agent uses when implementing any feature or bugfix, before writing implementation code

    5.6k GitHub starsUsed in 51 repos~2.5k tokens
    Testing & QAAuto-check passed
  • Tapd Story Pipeline

    TencentBlueKing/bk-bcs

    单需求实现流水线——把一个 TAPD 需求从零推进到代码提交。自动串联技术澄清、 开发计划、任务拆分、TDD 实现、架构/安全校验、代码提交六个阶段。

    840 GitHub stars~2.6k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Absolute Init

    maddhruv/absolute

    One-time setup for absolute: interview how you want it to behave (output style, autonomy, TDD strictness, spec dir, families) + detect the stack once, then write .absolute.config.json (project…

    219 GitHub starsUsed in 1 repo~3k tokens
    Testing & QAAuto-check passed

More from parcadei/Continuous-Claude-v3

All 141 skills in this repo
  • Compound Learnings

    parcadei/Continuous-Claude-v3

    Transform session learnings into permanent capabilities (skills, rules, agents).

    3.9k GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check: notes
  • Debug Hooks

    parcadei/Continuous-Claude-v3

    Systematic hook debugging workflow. An agent skill from parcadei/Continuous-Claude-v3.

    3.9k GitHub starsUsed in 1 repo~863 tokens
    Auto-check: notes
  • Tldr Deep

    parcadei/Continuous-Claude-v3

    Full 5-layer analysis of a specific function. An agent skill from parcadei/Continuous-Claude-v3.

    3.9k GitHub starsUsed in 1 repo~677 tokens
    Auto-check passed
  • Gradient Methods

    parcadei/Continuous-Claude-v3

    Problem-solving strategies for gradient methods in optimization

    3.9k GitHub starsUsed in 2 repos~1k tokens
    Auto-check: notes
  • Math

    parcadei/Continuous-Claude-v3

    Unified math capabilities - computation, solving, and explanation.

    3.9k GitHub starsUsed in 2 repos~1.6k tokens
    Auto-check: notes
  • Math Model Selector

    parcadei/Continuous-Claude-v3

    Routes problems to appropriate mathematical frameworks using expert heuristics

    3.9k GitHub starsUsed in 2 repos~841 tokens
    Auto-check passed

Categories

Questions about TDD Migration Pipeline

What does TDD Migration Pipeline do?

Orchestrator-only workflow for migrating/rewriting codebases with full TDD and agent delegation. TDD Migration Pipeline is an agent skill from parcadei/Continuous-Claude-v3.

When should I use TDD Migration Pipeline?

TDD Migration Pipeline fits situations like: tasks that involve Test-driven development.

How do I install TDD Migration Pipeline in Claude Code?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migration-pipeline -a claude-code`. Or copy the skill folder (.claude/skills/tdd-migration-pipeline in parcadei/Continuous-Claude-v3) into .claude/skills/tdd-migration-pipeline in your project. Claude Code loads it when a task matches its description.

How do I install TDD Migration Pipeline in Codex?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migration-pipeline -a codex`. Or copy the skill folder (.claude/skills/tdd-migration-pipeline in parcadei/Continuous-Claude-v3) into .agents/skills/tdd-migration-pipeline in your project. Codex loads it when a task matches its description.

Can I use TDD Migration Pipeline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migration-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tdd-migration-pipeline, .gemini/skills/tdd-migration-pipeline, .github/skills/tdd-migration-pipeline and .opencode/skills/tdd-migration-pipeline in your project.

What does TDD Migration Pipeline need to run?

SKILL.md names no scripts, command-line tools or credentials: TDD Migration Pipeline is instructions for the agent only. Its frontmatter pre-approves these tools: Task, TodoWrite, Read, Bash.

Does TDD Migration Pipeline access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is TDD Migration Pipeline safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does TDD Migration Pipeline use?

TDD Migration Pipeline is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does TDD Migration Pipeline use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to TDD Migration Pipeline?

Skills that share tags, products or a category with TDD Migration Pipeline: TDD (pietheinstrengholt/rssmonster, 564 stars), TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), TDD (sanity-io/sanity, 6.4k stars) and Test Driven Development (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains TDD Migration Pipeline?

parcadei (a GitHub user) maintains it in parcadei/Continuous-Claude-v3, which has 3,943 GitHub stars. The repository holds 141 skills in this directory. The repository was last updated on January 26, 2026.

Source: parcadei/Continuous-Claude-v3 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.