What problem does it solve? Designing a new NestJS module without a clear structure leads to coupled layers, circular dependencies, and inconsistent patterns across the codebase. This Skill enforces a strict Clean Architecture / DDD layout (presentation, domain, data) and persists the full design as a plan document instead of flooding the chat. ## Core Features & Use Cases - Architecture Planning: Defines module structure with strict layer separation, abstract-class DI tokens, and TypeORM persistence strategy, written to .agents/plans/<name>.md. - Automated Scaffolding: Runs scripts/scaffold_module.sh to generate domain interfaces, abstract service/repository contracts, and the NestJS module file in dependency-safe order. - Circular Dependency Verification: Validates the generated module with npx madge --circular, with a manual layer-rule fallback when madge is unavailable. - Use Case: Ask the agent to design a new payment-requests module; it scaffolds the contracts, writes the architecture plan to disk, and replies in chat with only a summary, gaps, and business questions. ## Quick Start Ask the agent to design the architecture for a new NestJS module named payment-requests following Clean Architecture.