Agent skill

TDD Migrate

by parcadei in parcadei/Continuous-Claude-v3

TDD workflow for migrations - orchestrate agents, zero main context growth

MITAuto-check: notesTesting & QA

Install TDD Migrate

skills CLI

$ npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migrate -a claude-code

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

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 tdd-migrate --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-migrate .claude/skills/tdd-migrate && 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/

Paste into Claude Code

Install the "tdd-migrate" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/tdd-migrate into .claude/skills/tdd-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tdd-migrate", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/tdd-migrate

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migrate -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 tdd-migrate --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "tdd-migrate" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/tdd-migrate into .agents/skills/tdd-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tdd-migrate", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migrate -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 tdd-migrate --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "tdd-migrate" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/tdd-migrate into .cursor/skills/tdd-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tdd-migrate", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/parcadei/Continuous-Claude-v3.git --path .claude/skills/tdd-migrate

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migrate -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 tdd-migrate --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "tdd-migrate" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/tdd-migrate into .gemini/skills/tdd-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tdd-migrate", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 tdd-migrate

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migrate -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

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

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "tdd-migrate" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/tdd-migrate into .github/skills/tdd-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tdd-migrate", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add parcadei/Continuous-Claude-v3 --skill tdd-migrate -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 tdd-migrate --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "tdd-migrate" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/tdd-migrate into .opencode/skills/tdd-migrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tdd-migrate", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: tdd-migrate
GitHub stars: 3.9k
Used in: 1 other repo
Token cost: ~1.4k tokens
SKILL.md length: 315 words
Files: 1
Skills in repo: 141
Repo updated: Jan 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

TDD workflow for migrations - orchestrate agents, zero main context growth

Works in 7 steps: Create YAML TODO → Launch Scout Agents (parallel) → Launch Kraken Agents (parallel per item) → …
Tasks that involve Test-driven development
SKILL.md covers When to Use, Parameters, Workflow and Key Principles, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

TDD Migrate is an agent skill from parcadei/Continuous-Claude-v3. TDD workflow for migrations - orchestrate agents, zero main context growth

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-migrate”

Requirements

Python 3
Pre-approved tools (allowed-tools): Task, TodoWrite, Write, Read, Bash

Workflow steps

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

Create YAML TODO
Launch Scout Agents (parallel)
Launch Kraken Agents (parallel per item)
Review + Validate (parallel)
Fix Issues
TLDR Diff
Update Continuity

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
- Write
- 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 and bash).
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 Migrate loads about 1.4k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 315 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~22
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, Write, 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). 315 words, ~1,416 tokens.

Download SKILL.mdSave it as .claude/skills/tdd-migrate/SKILL.md (or your agent's skills folder).

name: tdd-migrate
description: TDD workflow for migrations - orchestrate agents, zero main context growth
allowed-tools: Task, TodoWrite, Write, Read, Bash

TDD Migrate

Orchestrate TDD migrations with agents doing all work. Main context stays clean.

When to Use

"Port X from Python to TypeScript"
"Create N adapters following existing pattern"
"Migrate module to new architecture"
"TDD implementation of multiple similar items"

Parameters

/tdd-migrate <source_path> <target_path> --pattern <reference> --items "item1,item2,item3"

source_path: Path to analyze (existing code)
target_path: Where to create new code
pattern: Reference file/pattern to follow
items: Comma-separated list of things to create

Workflow

Phase 0: YAML TODO List
    │
    ▼
Phase 1: TLDR Analysis ─────────────────┐
    │                                    │
    ▼                                    │ Parallel scouts
Phase 2: Write Failing Tests ───────────┤ per item
    │                                    │
    ▼                                    │
Phase 3: Implement (minimal) ───────────┤
    │                                    │
    ▼                                    │
Phase 4: Build + Pass Tests ────────────┘
    │
    ▼
Phase 5: QLTY Check ────────────────────┐
    │                                    │ Parallel
Phase 6: Review Agent Validates ────────┘
    │
    ▼
Phase 7: TLDR Diff (new vs reference)
    │
    ▼
Phase 8: Fix Issues (if any)
    │
    ▼
Complete

Key Principles

Main context = orchestration only
- Never read files directly (use scout)
- Never implement directly (use kraken/spark)
- Never run tests directly (use validator)
- Only pipe context and coordinate
Agents do ALL work

Task Agent
Explore/analyze scout
Write tests + implement kraken
Quick fixes spark
Run tests/validate validator
Code review critic
Parallel where independent
- All items can be implemented in parallel if independent
- Review + QLTY run in parallel
- TLDR analysis runs in parallel with planning
Review after each major step
- After implementation: critic reviews
- After fixes: validator re-validates

Task	Agent
Explore/analyze	scout
Write tests + implement	kraken
Quick fixes	spark
Run tests/validate	validator
Code review	critic

Instructions

Step 0: Create YAML TODO

Write a YAML plan file to thoughts/shared/plans/<name>-tdd.yaml:

yaml

---
title: <Migration Name>
date: <today>
type: implementation-plan
approach: TDD (test → build → pass → review)

items:
  - name: item1
    file: <target_path>/item1.ts
    test: <target_path>/__tests__/item1.test.ts
    deps: []
  - name: item2
    # ...

reference: <pattern_file>

workflow:
  per_item:
    1: Write failing test
    2: Implement minimal
    3: Build
    4: Pass test
    5: QLTY check
    6: Review
  final:
    7: Integration test
    8: TLDR diff

Step 1: Launch Scout Agents (parallel)

Task (scout): Analyze <source_path> with TLDR
Task (scout): Analyze <pattern> to understand structure
Task (scout): Read migration handoff if exists

Step 2: Launch Kraken Agents (parallel per item)

For each item, launch ONE kraken that does full TDD:

Task (kraken): Implement <item> using TDD workflow
  1. Read pattern file
  2. Write failing test
  3. Implement
  4. Run: bun test <test_file>
  5. Run: qlty check <impl_file>

Step 3: Review + Validate (parallel)

Task (critic): Review all new files against pattern
Task (validator): Run full test suite
Task (validator): QLTY check all files

Step 4: Fix Issues

If critic/validator found issues:

Task (spark): Fix <specific issue>
Task (validator): Re-validate

Step 5: TLDR Diff

Task (validator): TLDR diff new files vs reference
  - tldr structure <new_file> --lang <lang>
  - tldr structure <reference> --lang <lang>
  - Compare patterns

Step 6: Update Continuity

Update ledger with completed work.

Example: Rigg Adapters

bash

/tdd-migrate /Users/cosimo/Documents/rigg/src/sdk/providers \
  /Users/cosimo/Documents/rigg/src/sdk/providers \
  --pattern lmstudio.ts \
  --items "xai,cerebras,togetherai,deepinfra,perplexity"

Resulted in:

5 parallel kraken agents
39 tests passing
All adapters working
~15 minutes total

Anti-Patterns (AVOID)

Bad	Good
Read files in main context	Launch scout agent
Write code in main context	Launch kraken/spark agent
Run tests in main context	Launch validator agent
Skip review	Always launch critic
Sequential items	Parallel krakens
Fix in main context	Launch spark

Agent Prompts

Scout (analysis)

Explore <path> to understand:
1. Structure/patterns
2. Interfaces/types
3. Dependencies
Return actionable summary for implementation.

Kraken (TDD)

Implement <item> using TDD:
1. Read <pattern> for structure
2. Write failing test to <test_path>
3. Implement minimal to <impl_path>
4. Run: <test_command>
5. Run: qlty check <impl_path>
Report: status, issues, files created.

Critic (review)

Review <files> against <pattern>:
1. Pattern compliance
2. Type safety
3. Missing registrations
4. Security issues
DO NOT edit. Report issues only.

Spark (fix)

Fix <specific issue>:
1. Read <file>
2. Make minimal edit
3. Verify fix

Validator (test)

Validate <files>:
1. Run <test_command>
2. Run qlty check
3. Report pass/fail/issues

Success Criteria

All tests pass
QLTY reports no issues
Critic found no critical issues
TLDR diff shows pattern compliance
All items registered/exported properly

Files

Just SKILL.md in .claude/skills/tdd-migrate 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.

vibeeval/vibecosystemskills/tdd-migrate

Compare with similar skills

TDD Migrate 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 Migrate compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
TDD Migrate this skillparcadei/Continuous-Claude-v3	3.9k	1 repos	~1.4k	Automated safety check: Notes	MIT	8 mo ago
TDDpietheinstrengholt/rssmonster	564	30 repos	~906	Automated safety check: Pass	MIT	yesterday
TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph	112	11 repos	~2.4k	Automated safety check: Pass	None	8 mo ago
TDDsanity-io/sanity	6.4k	20 repos	~1k	Automated safety check: Pass	MIT	today
Test Driven Developmentfarm-fe/farm	5.6k	51 repos	~2.5k	Automated safety check: Pass	MIT	17 days ago
Tapd Story PipelineTencentBlueKing/bk-bcs	841	—	~2.6k	Automated safety check: Pass	Custom licence	yesterday

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
Test Driven Development
farm-fe/farm
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 实现、架构/安全校验、代码提交六个阶段。
841 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…
218 GitHub starsUsed in 1 repo~3k tokens
Testing & QAAuto-check passed

Questions about TDD Migrate

What does TDD Migrate do?

TDD workflow for migrations - orchestrate agents, zero main context growth. TDD Migrate is an agent skill from parcadei/Continuous-Claude-v3.

When should I use TDD Migrate?

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

How do I install TDD Migrate in Claude Code?

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

How do I install TDD Migrate in Codex?

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

Can I use TDD Migrate 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-migrate -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-migrate, .gemini/skills/tdd-migrate, .github/skills/tdd-migrate and .opencode/skills/tdd-migrate in your project.

What does TDD Migrate need to run?

SKILL.md names no scripts, command-line tools or credentials: TDD Migrate is instructions for the agent only. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Task, TodoWrite, Write, Read, Bash.

Does TDD Migrate 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 Migrate 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 Migrate use?

TDD Migrate 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 Migrate use?

About 1.4k tokens (SKILL.md is roughly 5.7k 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 Migrate?

Skills that share tags, products or a category with TDD Migrate: 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 Migrate?

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.

Install TDD Migrate

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

TDD Migrate

When to Use

Parameters

Workflow

Key Principles

Instructions

Step 0: Create YAML TODO

Step 1: Launch Scout Agents (parallel)

Step 2: Launch Kraken Agents (parallel per item)

Step 3: Review + Validate (parallel)

Step 4: Fix Issues

Step 5: TLDR Diff

Step 6: Update Continuity

Example: Rigg Adapters

Anti-Patterns (AVOID)

Agent Prompts

Scout (analysis)

Kraken (TDD)

Critic (review)

Spark (fix)

Validator (test)

Success Criteria

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from parcadei/Continuous-Claude-v3

Related

Questions about TDD Migrate