sprouting-instead-of-editing

Generate new tested code units for legacy code changes.

3|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill sprouting-instead-of-editing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprouting-instead-of-editing
Source: https://github.com/cwijayasundara/claude_harness_eng_v5/tree/main/.claude/skills/sprouting-instead-of-editing
Command: npx skills add https://github.com/cwijayasundara/claude_harness_eng_v5 --skill sprouting-instead-of-editing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents direct modifications to legacy code by automatically sprouting new, fully tested units to handle required changes.

Core Features & Use Cases

  • Automatic Sprouting: Automatically generates new code units for modifications in legacy code.
  • Safety Check: Ensures only one call line in the legacy code is modified, preventing unintended changes.
  • TDD Compliant: Ensures the new sprouted code is fully tested and TDD compliant.

Quick Start

Run the 'sprout-instead-of-editing' skill when you encounter a change that must be made to an uncovered legacy function.

Frequently Asked Questions about sprouting-instead-of-editing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update legacy code without modifying the existing source files?

You can sprout new units to handle required changes instead of altering existing legacy code. This approach modifies only a single call line in the legacy code to invoke the new unit, ensuring the original logic remains untouched.

What is code sprouting in test-driven development?

Code sprouting is a test-driven development technique for adding functionality by creating fully tested new units rather than editing uncovered legacy code. It introduces changes safely without requiring tests for the entire legacy function.

How do I add features to uncovered legacy code using TDD?

Add features to uncovered legacy code by sprouting a new unit for the modification and developing it through a TDD process. The original legacy code remains unmodified except for a single safety-checked call line invoking the newly tested unit.

Can I refactor legacy code without altering existing logic?

Yes, you can sprout new units for required changes to refactor legacy code without altering existing logic. This method modifies only one call line to route to the new unit, preventing unintended changes to the original codebase.

When should I use the code sprouting technique for software maintenance?

Use code sprouting when a required change targets an uncovered legacy function during software maintenance. It is ideal when refactoring or updating is necessary but modifying existing code poses high regression risks.