nacl-tl-dev-be

Automates backend feature delivery from UC plans with strict RED-GREEN-REFACTOR workflow.

23|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-dev-be
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nacl-tl-dev-be
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-tl-dev-be
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-dev-be

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend development often stalls after planning; this skill provides a disciplined TDD-driven workflow to implement backend features directly from task specs, ensuring tests drive design and progress traceability.

Core Features & Use Cases

  • Read backend task files from .tl/tasks/UC### and follow a strict RED -> GREEN -> REFACTOR workflow.
  • Implement API endpoints, services, repositories, DTOs, migrations, and documentation as per the task brief.
  • Generate a result-be.md with a complete experimental log and update tracking files.

Quick Start

Run /nacl-tl-plan to fetch the UC task, then follow the RED–GREEN–REFACTOR cycle to implement the backend feature.

Frequently Asked Questions about nacl-tl-dev-be

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

FAQPage Schema
How do I implement backend features using a strict TDD workflow?

To implement backend features using TDD, read task specs from .tl/tasks/UC### and follow a strict RED-GREEN-REFACTOR cycle, creating failing tests first, writing minimal code to pass, and refactoring. It generates a result-be.md log and updates tracking files.

What is the best way to drive API contract design from test specs?

Driving API contract design from test specs involves writing failing tests first based on the task brief, then implementing minimal endpoints, services, and DTOs to pass, ensuring tests dictate the API design.

How do I generate documentation and track status after backend development?

Generate documentation and track status by producing a result-be.md file containing the complete experimental log, then automatically updating the task status and changelog tracking files upon completing the TDD cycle.

Can I use this workflow to implement backend tasks defined in UC plans?

Yes, you can use this workflow to implement backend tasks defined in UC plans by running /nacl-tl-plan to fetch the task, then applying the TDD cycle to deliver the specified endpoints, services, and repositories.

What is the RED-GREEN-REFACTOR cycle in backend development?

The RED-GREEN-REFACTOR cycle in backend development is a TDD process where you create failing tests first, implement minimal code to pass those tests, and then refactor the codebase while maintaining test coverage.

Do I need to manually update the changelog after finishing a backend task?

No, you do not need to manually update the changelog after finishing a backend task; the workflow automates generating the result-be.md experimental log and updating both the changelog and status tracking files.