jikime-workflow-ddd

Implement a Domain-Driven Development workflow for behavior-preserving code transformation.

5|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jikime/jikime-adk --skill jikime-workflow-ddd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jikime-workflow-ddd
Source: https://github.com/jikime/jikime-adk/tree/main/templates/.claude/skills/jikime-workflow-ddd
Command: npx skills add https://github.com/jikime/jikime-adk --skill jikime-workflow-ddd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of refactoring legacy codebases by ensuring that existing behavior is preserved throughout the modernization process, reducing the risk of introducing regressions.

Core Features & Use Cases

  • Behavior Preservation: Guarantees that code changes do not alter observable functionality through characterization tests and snapshots.
  • Incremental Refactoring: Facilitates safe, step-by-step structural improvements using AST-grep for precise transformations.
  • Use Case: Modernize a critical backend service by improving its internal structure for better maintainability, without changing its API responses or core business logic.

Quick Start

Run the jikime-workflow-ddd skill to analyze and refactor the codebase for improved structure while preserving behavior.

Frequently Asked Questions about jikime-workflow-ddd

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

FAQPage Schema
How do I refactor legacy code without changing existing behavior?

Incremental refactoring of legacy code applies AST-grep for structural analysis and characterization tests to preserve behavior. This step-by-step approach reduces technical debt without altering observable functionality.

What is the best way to reduce technical debt in a critical backend service?

The best way to reduce technical debt is applying incremental structural improvements using AST-grep transformations. This modernizes internal code structure for better maintainability without changing core business logic or API responses.

Do I need AST-grep to perform behavior-preserving code transformations?

Yes, AST-grep is required for structural analysis and precise code transformations during the IMPROVE phase. It enables safe structural modifications by analyzing the abstract syntax tree of the legacy codebase.

How does a characterization test work during API migration?

Characterization tests validate behavior preservation during API migration by capturing current functionality snapshots. They ensure that structural improvements and transformations do not introduce regressions or alter observable functionality.

When should I not use AST-grep for refactoring legacy code?

AST-grep refactoring may not suit non-structural code changes or when characterization tests cannot be established. Without baseline behavior validation, structural transformations risk introducing unobserved regressions in legacy systems.