What problem does it solve? Starting a .NET feature or solution without written requirements leads to rework, hidden assumptions, and architectural decisions made on the fly. This Skill enforces a gated Specify → Plan → Tasks → Implement workflow so requirements are validated by a human before any code is written. ## Core Features & Use Cases - Four-phase gated workflow: Specify, Plan, Tasks, and Implement, each requiring human review before advancing. - .NET-specific spec template: Covers objective, dotnet CLI commands, solution structure (Core/Infrastructure/Contracts projects), code style, xUnit/MSTest testing strategy, and Always/Ask First/Never boundaries. - Assumption surfacing and reframing: Translates vague requests like "make the app faster" into testable success criteria for Avalonia, ASP.NET Core, Blazor, MAUI, and EF Core scenarios. - Use Case: When asked to add a new feature to an Avalonia 11 desktop app, the Skill first lists assumptions (.NET 8, EF Core 8, xUnit v3, CommunityToolkit.Mvvm), drafts a spec saved to docs/specs/, and only proceeds to implementation after approval. ## Quick Start Ask the agent to write a specification for your new .NET feature before any code is written, describing the goal and letting it surface assumptions for your review.
