dotnet-implementer-prompt

Dispatch a .NET backend implementer subagent with a strict TDD workflow.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/fiatkongen/saurun-marketplace --skill dotnet-implementer-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-implementer-prompt
Source: https://github.com/fiatkongen/saurun-marketplace/tree/main/plugins/saurun/skills/dotnet-implementer-prompt
Command: npx skills add https://github.com/fiatkongen/saurun-marketplace --skill dotnet-implementer-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured prompt template to dispatch a .NET backend implementer subagent, ensuring complete context, adherence to TDD, and thorough self-review before reporting back.

Core Features & Use Cases

  • Structured task prompts for .NET backend implementations, enabling precise task instructions and consistent results.
  • Context-first dispatch ensures the subagent receives all necessary system, domain, and architectural details without reading external plans.
  • TDD & self-review enforcement guarantees red-green-refactor cycles and pre-report quality checks for each task.

Quick Start

To begin, paste a full task description into the Task tool using this prompt. Include the Task Description, Context, the absolute working directory, and a reference to saurun:dotnet-tdd for the testing checklist. Working from the backend root path ensures correct relative references.

Frequently Asked Questions about dotnet-implementer-prompt

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

FAQPage Schema
How do I dispatch a subagent for .NET backend implementation with TDD?

To dispatch a .NET backend implementer subagent, use this prompt template to pass full task descriptions, project context, and an absolute working directory. It enforces a strict TDD workflow and self-review before returning a structured report.

What is the best way to enforce test-driven development on an ad-hoc .NET task?

Enforcing test-driven development on ad-hoc .NET tasks requires a structured prompt that mandates red-green-refactor cycles. This skill provides that structure, referencing a specific dotnet-tdd checklist to verify testing compliance before reporting back.

Do I need to provide external plan files when dispatching a .NET subagent?

No external plan files are needed when dispatching the .NET subagent. The prompt operates context-first, meaning you embed all necessary system, domain, and architectural details directly in the task description for the subagent.

How does a .NET subagent prompt handle self-review and reporting?

A .NET subagent prompt handles self-review by enforcing mandatory pre-report quality checks within its structured sections. It guarantees the subagent completes the TDD cycle and reviews its work before outputting a final structured report.

What context should I include when assigning a backend implementation task to a subagent?

Include the Task Description, Context (system and domain details), the absolute working directory, the TDD requirement, Self-Review criteria, and the Report Format. Working from the backend root path ensures correct relative references.

Can I use this prompt dispatch for non-backend .NET development tasks?

This prompt dispatch is specifically tailored for .NET backend implementation tasks. It focuses on backend architectural details and enforces a strict TDD workflow, making it less suitable for non-backend development scenarios.