coder:clone-behavior

To clone software behavior without copying source, you extract functional behaviors into a BEHAVIOR.md file and reimplement the logic from scratch. This approach produces idiomatic target-language code that preserves the original program's functionality.

Rewriting a project in a different programming language while keeping functionality requires a phase-driven process: SCAN, PLAN, IMPLEMENT, VERIFY, and COMPLETE. This ensures the new codebase is idiomatic to the target language and passes verification reporting against original behaviors.

Yes, generating a ROADMAP is a required phase before implementation in a behavior-driven code rewrite. It structures the reimplementation process alongside BEHAVIOR.md requirements to ensure all extracted functionalities are systematically tracked and rebuilt.

Behavior extraction focuses on documenting what a program does rather than how it is written, avoiding direct code translation pitfalls. This allows a clean, idiomatic reimplementation in the target language instead of porting syntax structures that may not fit.

Yes, you can verify that a rewritten module matches the original software's behavior through the VERIFY phase. This step generates a CLONE-VERIFICATION report to confirm the production-grade reimplementation satisfies the explicit BEHAVIOR.md requirements.

If a behavior clone is not passing verification, you should revisit the SCAN and PLAN phases to ensure the BEHAVIOR.md accurately captures the original module's requirements. The CLONE-VERIFICATION report will highlight where the reimplementation diverges from expected functionality.