nestjs-domain-delivery

What problem does it solve?

NestJS changes can blur module boundaries and lifecycles, making it easy to ship broken wiring, mismatched DTO/OpenAPI, unsafe transactions/queue ordering, or unproven guards/pipes—especially when AI-driven edits lack evidence and scoped verification.

Core Features & Use Cases

• Module-graph delivery: Produces an explicit moduleGraph with ownership (imports/exports/providers/controllers) and flags circular dependency risks before edits.
• Request-pipeline correctness: Plans httpContract for routes, DTO validation, guards, interceptors, filters, and OpenAPI responses so they match actual behavior.
• Runtime-safe side effects: Plans providerPlan plus transactionPlan and queuePlan, including commit ordering, outbox/idempotency expectations, and rollback behavior.
• Evidence-first verification: Requires a focused Nest/Jest unit/e2e verificationCommands set and blocks completion when scoped evidence or approvals are missing.

Quick Start

Ask your AI tool to apply this NestJS domain delivery skill to the smallest owned behavior slice in your existing project, using the skill’s evidence-first dry run and scoped command, and only proceed when the results match expectations.