csharp-tdd-develop_skill

This skill coordinates test-first C# development by enforcing red green refactor phases and delegating work to a sub-agent for reliable code.

PowerShell

4

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill jeongheonk/c-sharp-custom-marketplace --skill csharp-tdd-develop

SKILL.md8.8 KB

Overview

This skill orchestrates a strict TDD workflow for C#/.NET projects, enforcing the Red-Green-Refactor cycle and delegating implementation tasks to sub-agents. It detects test environment from .csproj, converts requirements into test scenarios, and coordinates test creation, minimal implementation, and refactoring with verification at each step.

How this skill works

The orchestrator runs an environment detector against .csproj files to confirm test runner and libraries (xUnit, FluentAssertions, Moq). It converts user requirements into a target class, test scenarios, and test file paths, then delegates RED, GREEN, and REFACTOR tasks to sub-agents using task prompts. Each phase requires automated verification (failing tests for RED, passing for GREEN, and regression-free tests after REFACTOR).

When to use it

You want to adopt strict TDD for a new or existing C#/.NET feature.
You need automated orchestration that enforces Red-Green-Refactor discipline.
You want to generate test scenarios and ensure tests fail before implementation.
You need delegable tasks for writing tests, implementing minimal code, and refactoring.
You must verify test environment (xUnit, FluentAssertions, Moq) before work begins.

Best practices

Run environment detection early; abort and install missing test packages if not present.
Convert requirements into 3–5 focused test scenarios before writing tests.
Enforce AAA pattern and Method_Scenario_ExpectedBehavior naming in tests.
Require failing tests in RED and passing tests in GREEN before refactoring.
Keep GREEN implementations minimal; reserve design improvements for REFACTOR.
Rollback changes automatically if tests fail after refactor.

Example use cases

Implementing a new UserService with tests generated and validated by the orchestrator.
Adding a ViewModel behavior with unit tests placed under tests/UnitTests/ViewModels.
Converting a bug report into failing tests (RED) then fixing with minimal code (GREEN).
Refactoring a repository implementation while ensuring no regressions via automated test runs.
Bootstrapping TDD workflows across a team that delegates work to sub-agents.

FAQ

The skill prints the required dotnet add package commands and stops until the environment is fixed.

What if tests already pass in RED?

The workflow halts and requests a scenario review because RED requires failing tests before implementation.