dotnet-writing-plans

A .NET implementation plan is a structured document of discrete tasks with file paths, expected behaviors, and dependencies. It is generated from a feature spec and saved as a markdown file to ensure architecture-aligned, TDD-driven delivery.

Aligning .NET tasks with architecture contracts means linking your generated implementation plan directly to established architecture rules. This ensures every discrete task, file path, and expected behavior maintains traceability with the system's structural design.

Yes, you can use this approach to plan TDD-driven delivery for multi-step .NET tasks. It translates product specs into staged plans outlining domain tasks, API contracts, and persistence changes, incorporating expected tests and behaviors per task.

The generated .NET plan includes only the task structure and not actual code implementation. It outputs a ready-to-use skeleton organized as discrete tasks with files, tests, behaviors, and dependencies to guide subsequent coding.

Structuring implementation plans for complex .NET features involves breaking them into discrete tasks. Each task section in the saved markdown document specifies required files, dependencies, and expected behaviors derived from the original feature spec.