deep-clone

---
name: deep-clone
description: "Start or continue a deep software clone by recovering the vendor's original implementation through a Hybrid version, feature test decks, a verifier, and an HTML workbench, and building Cloned software from the same source. Use for implementation recovery rather than reproducing an interface or visible features alone."
---

# Deep Clone

Start or continue a deep clone of vendor software. Read the [method](references/method.md) for the task definition, terminology, limitations, and examples.

## Start or resume

For an existing project, resume from its README, local methodology, and HTML workbench. Check the source and active processes; preserve existing work. For a new project, follow the [workbench template](../deep-clone-workbench/assets/project-template/README.md#create-a-project) to install the methodology and entry points in the workspace. The [workflow](references/workflow.md) gives the full sequence.

Do not load the REA skill by default. Use it only when the user explicitly requests it. Record the current preference, including the default, in the project's `AGENTS.md` or existing repository-local agent instructions. Read it on resume and update it when the user changes their choice.

Create or resume an actual goal under the [continuous execution principle](references/workflow.md#continuous-execution-set-a-goal-and-continue-unless-blocked). Continue unless genuinely blocked. With no feature preference, choose a common feature and build a minimal deck. Load only the skills needed for the current task.

## Three stages

| Stage | Work and entry points |
| --- | --- |
| Build the foundation | Prepare the [vendor and binary tools](../deep-clone-binary/SKILL.md), [recovery scope](../deep-clone-scope/SKILL.md), [test decks](../deep-clone-test-decks/SKILL.md), [runtime integration](../deep-clone-runtime/SKILL.md), [verifier](../deep-clone-verifier/SKILL.md), and [HTML workbench](../deep-clone-workbench/SKILL.md). Failed [prerequisites](references/workflow.md#stage-1-build-working-infrastructure) must produce an error. |
| Work mainly in a Hybrid version | Build a deck → [recover and substitute functions](../deep-clone-runtime/SKILL.md) → [run and compare](../deep-clone-verifier/SKILL.md) → [locate the divergence](../deep-clone-difference/SKILL.md) → continue recovery. Start with important functions and actual call counts; expand substitution coverage. |
| Form Cloned software | Try a minimal Cloned software v1 during Hybrid recovery; follow the [transition](references/workflow.md#transition-from-hybrid-to-cloned-software) to shift focus or continue improving Hybrid. Reuse the same source for both builds, iterate to exact agreement, and retain Hybrid as coverage expands. |

Organize source by the [original binary and probed symbols](../deep-clone-runtime/SKILL.md#required-source-organization-and-naming). Use the HTML workbench to synchronize people and sessions. Other record formats are project choices. Apply the [evidence lifecycle](references/workflow.md#evidence-lifecycle) as functions are completed.

[Reporting and handoff](../deep-clone-reporting/SKILL.md) continue throughout recovery. [Code review](../deep-clone-review/SKILL.md) checks fidelity. Once development is complete, follow the [submission workflow](../deep-clone-submit/SKILL.md) within the user's authorization.

• SKILL.md 3 KB
• references/method.md 6 KB
• references/workflow.md 11 KB