What problem does it solve? Manually creating CQRS command handlers across bounded contexts involves repetitive boilerplate and risks inconsistent patterns. This Skill generates the complete set of files—command record, result type, handler class, and DI registration—following the project's established sealed record and static factory conventions. ## Core Features & Use Cases - Full Handler Scaffolding: Creates the ICommandHandler interface (first use only), command record, result type, handler class, and DI registration line in one workflow. - Flexible Result Types: Supports enum results for simple state outcomes and sealed records with static factories for rich outcomes carrying data like entity IDs. - Convention Enforcement: Ensures handlers are internal sealed, commands are immutable sealed records, and business logic stays out of records and results. - Use Case: When adding a new CancelOrder operation to the Sales/Orders bounded context, generate the command, result, handler, and registration in seconds instead of hand-writing four files. ## Quick Start Ask the AI to create a CQRS command handler named CancelOrder in the Sales/Orders bounded context with an enum result type.
