add-command

Add CQRS Command

When the user asks to add a new command, scaffold the following files in the correct microservice. Ask which service if ambiguous.

If the command involves non-trivial FluentValidation rules (async validators, cross-field validation, collection rules) or WolverineFx middleware, use context7 to look up the current docs before writing.

Arguments

• {Name} -- Command name in PascalCase (e.g., CreateOrder, AssignRole)
• {Service} -- Target microservice. Ask if ambiguous.

Configuration

Read cloudstack.json from the project root at the start of execution. Extract:

• NAMESPACE = project.namespace (default: detect from *.sln name or first *.csproj root namespace)
• SERVICES = backend.services[] (default: discover from src/*/ directories containing .Application/ subfolders)
• SOLUTION = backend.solutionPath (default: find *.sln in src/)

If cloudstack.json does not exist, auto-detect by scanning the project structure.

Prerequisites

• The target microservice must exist under src/
• An Endpoints file should exist at Host/Endpoints/ (if not, create one)
• If the command operates on an entity that doesn't exist yet, run /add-entity first

1. Command Record (Application/Commands/{CommandName}.cs)

namespace {Namespace}.{Service}.Application.Commands;

public record {Name}Command({parameters});

2. Response Record (same file or Application/Contracts/)

public record {Name}Response({response fields});

3. Handler (Application/Commands/{Name}Handler.cs)

namespace {Namespace}.{Service}.Application.Commands;

public class {Name}Handler
{
    // Constructor-inject repositories and services

    public async Task<Result<{Name}Response>> Handle({Name}Command command, CancellationToken cancellationToken)
    {
        // 1. Validate business rules
        // 2. Create/modify domain entities via factory methods or aggregate methods
        // 3. Persist via repository
        // 4. Return Result.Success or Result.Failure with SCREAMING_SNAKE error code
    }
}