reverse-engineer-strategies

Analyze Kotlin and Spring Boot codebases to generate strategies documentation.

2|Updated Apr 17, 2026

Search Tags:#documentation #kotlin #code-analysis #spring-boot #reverse-engineering #strategies

Ready to run

npx skills add https://github.com/wooyong99/claude-code-playbook --skill reverse-engineer-strategies

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reverse-engineer-strategies
Source: https://github.com/wooyong99/claude-code-playbook/tree/main/.claude/skills/reverse-engineer-strategies
Command: npx skills add https://github.com/wooyong99/claude-code-playbook --skill reverse-engineer-strategies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill analyzes an existing Kotlin + Spring Boot backend codebase to automatically generate the claude-code-playbook's strategies documentation, aligning playbook conventions with real code and eliminating manual drafting.

Core Features & Use Cases

Analyze a codebase to identify architectural layers (domain, application, storage, external, app) and generate per-layer strategies/README.md and convention docs.
Merge with existing documentation when requested, or create new docs for new layers in line with code patterns.
Update and standardize the strategies files to reflect actual classes and patterns found in the codebase.

Quick Start

Analyze the target codebase and generate strategies documentation into the project’s docs/backend/architecture area.

Frequently Asked Questions about reverse-engineer-strategies

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

FAQPage Schema

How do I generate architecture documentation for an existing Kotlin Spring Boot project?▼

You can generate architecture documentation for a Kotlin Spring Boot project by analyzing the codebase to identify domain, application, storage, external, and app layers, then automatically outputting per-layer convention docs and README files that reflect actual implementation patterns.

What is the best way to reverse-engineer codebase strategies for a legacy Spring Boot backend?▼

Reverse-engineering codebase strategies for a legacy Spring Boot backend involves reading existing code to extract architectural patterns and class names, then automatically generating standardized strategies documentation that aligns with the actual codebase implementation.

Can I merge newly generated strategies documentation with existing docs in my backend project?▼

Yes, you can merge newly generated strategies documentation with existing docs in your backend project. The analysis process can update and standardize existing files or create new docs for newly identified layers while preserving current content.

Does this codebase analysis tool require any specific dependencies to generate Spring Boot convention docs?▼

No specific dependencies are required to generate Spring Boot convention docs. The tool operates by reading the existing Kotlin and Spring Boot code directly and referencing internal templates to produce the architecture documentation.

Where should I output the generated per-layer architecture strategies and README files?▼

Generated per-layer architecture strategies and README files should be output or updated under the docs/backend/architecture/ directory path within your project structure to maintain standard documentation organization.

What code patterns and architectural layers are identified when analyzing a Kotlin backend codebase?▼

When analyzing a Kotlin backend codebase, the tool identifies domain, application, storage, external, and app architectural layers, extracting actual class names and implementation patterns to produce accurate per-layer convention documentation.