layer-architect

What problem does it solve?

This Skill translates high-level business rules into concrete implementation plans across a hexagonal architecture. It analyzes existing code for impact and strategically decides between TDD (Test-Driven Development) for modifications or Doc-Driven for new features, ensuring efficient and safe development.

Core Features & Use Cases

• Impact Analysis: Utilizes Serena MCP to search existing code, identifying which files need modification or are new, and assessing the impact on different layers of the architecture.
• Layer Mapping: Maps detailed business rules to specific components within the Domain, Application, Persistence, and REST API layers, providing a clear blueprint for implementation.
• Strategic Implementation Decision: Determines whether to apply TDD for modifying existing code (ensuring safety and preventing regressions) or Doc-Driven development for new code (for rapid, convention-based generation).
• Prioritized Implementation Order: Establishes a logical, dependency-based sequence for implementing tasks across layers, optimizing workflow and minimizing integration issues.
• Use Case: After requirements analysis, use this skill to generate a detailed implementation plan. This includes which layers are affected, what components to build, and the optimal strategy (TDD/Doc-Driven) for each task, allowing you to start coding with a clear roadmap.

Quick Start

Map the 'Order Cancellation' feature to hexagonal layers, analyze existing code impact, and propose an implementation strategy.