Where are the implementation plans stored?

All plans are automatically saved to the '_docs/plans/' directory using a YYYY-MM-DD-feature-name.md naming convention for easy tracking and documentation.

How does this skill interact with Test-Driven Development?

It generates plans that explicitly mandate the use of the 'saurun:dotnet-tdd' sub-skill to implement each task, ensuring high code quality and test coverage.

Which .NET versions and libraries are supported?

The skill is optimized for .NET 9, ASP.NET Core, EF Core 9, SQLite, xUnit, and NSubstitute, though the planning structure can be adapted for similar C# stacks.

What is a .NET writing plan?

A .NET writing plan is a structured architectural blueprint that breaks down complex backend tasks into individual, testable steps with defined behaviors and file paths before any code is written.

Should I use this for simple bug fixes?

No, this skill is specifically for multi-step features. Single-file bug fixes, configuration changes, or simple file renames do not require a formal implementation plan.

.NET Architecture Implementation Plans

Name: .NET Architecture Implementation Plans
Author: fiatkongen

byfiatkongen

0•

API Development

Generates structured, blueprint-first implementation plans for .NET backend tasks based on existing architectural specifications.

The dotnet-writing-plans skill streamlines the transition from architectural design to code execution by creating standardized, task-based implementation plans for .NET 9 backends. It acts as a bridge between high-level specs and Test-Driven Development (TDD), ensuring every file, contract, and behavior is accounted for before a single line of production code is written. By enforcing strict file paths, contract references, and dependency mapping, it minimizes architectural drift and optimizes token usage for autonomous coding agents while ensuring consistent project structure across domain entities, API endpoints, and infrastructure.

Key Features

01Seamless integration with saurun:dotnet-tdd for behavior-driven code generation

020 GitHub stars

03Standardized implementation plan generation following architectural contracts

04Token-optimized plan structure that avoids redundant code duplication

05Automated file path mapping for domain entities, API endpoints, and infrastructure

06Mandatory test infrastructure setup tasks for xUnit and NSubstitute

Use Cases

01Bridging the gap between an architecture specification document and a TDD-driven implementation workflow

02Planning multi-step features like new REST API endpoints or complex domain aggregates

03Organizing complex backend migrations and data persistence logic using EF Core 9

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add fiatkongen/saurun-marketplace dotnet-writing-plans

For use in Claude.ai and ChatGPT

Download Skill