nestjs-write-code

Orchestrates approved NestJS backend plans into TDD-verified code with mandatory checks.

2|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill nestjs-write-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nestjs-write-code
Source: https://github.com/sdcorejs/sdcorejs-agent/tree/main/plugin/skills/nestjs-write-code
Command: npx skills add https://github.com/sdcorejs/sdcorejs-agent --skill nestjs-write-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts an approved NestJS backend plan into working backend implementation while preserving SDLC conventions, safety gates, and verification steps so acceptance criteria don’t silently drift.

Core Features & Use Cases

  • Plan task orchestration: Walks the approved plan task-by-task in order, applying changes only within the plan scope.
  • TDD-first code writing: Writes failing unit/e2e tests before production edits, then re-runs tests to confirm “GREEN”.
  • Baseline convention enforcement: Applies NestJS baseline patterns (entities extend BaseEntity, services extend BaseService, guard order, DTO + Zod validation contracts, bilingual error messages, transactions, migrations).
  • Mandatory verification tail-call chain: Ensures e2e tests, code review, repair-loop iterations, comment gating, acceptance verification, auto-docs, task tracking, and optional memories.

Quick Start

Run nestjs-write-code after sdcorejs-review-plan approves a NestJS plan to generate the backend code following the plan tasks and mandatory verification steps.

Frequently Asked Questions about nestjs-write-code

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

FAQPage Schema
How do I generate NestJS backend code from an approved plan?

Writing NestJS backend code with TDD involves creating failing unit and e2e tests first, then making production edits to achieve GREEN status while enforcing baseline patterns like BaseEntity, BaseService, and Zod validation contracts.

What NestJS conventions are enforced during backend code generation?

NestJS backend code generation enforces baseline conventions where entities extend BaseEntity, services extend BaseService, guard order is maintained, DTOs use Zod validation contracts, errors are bilingual, and database transactions and migrations are applied.

How does TDD verification work for NestJS backend implementation?

TDD verification for NestJS backend implementation requires writing failing unit and e2e tests before production edits, then re-running tests to confirm GREEN status, ensuring acceptance criteria do not silently drift during code generation.

Do I need an approved plan before starting NestJS backend code generation?

Yes, you need an approved plan before starting NestJS backend code generation, because this Skill applies when orchestration has snapshotted the plan into the project and the user confirms readiness to proceed with backend implementation.

What verification steps are mandatory after writing NestJS backend code?

Mandatory verification steps after writing NestJS backend code include a tail-call chain ending in e2e tests, code review, repair-loop iterations, comment gating, acceptance verification, auto-docs, task tracking, and optional memories.