What problem does it solve? Adding a new event or command subscriber to a CoreEx solution normally requires coordinating many separate pieces — DTO contracts, database migrations, repositories, application services, the subscriber handler itself, and integration tests — while remembering which pieces apply to which messaging scenario. This Skill orchestrates that entire vertical slice in one guided workflow so nothing is missed and no question is asked twice. ## Core Features & Use Cases - Scenario-aware orchestration: Detects whether the subscriber is a command handler, an event-data-sync replication, or a business-process choreography, and runs only the applicable L1 skills (contract, migration, repository, app-service, subscriber, tests). - Upfront context gathering: Reads the solution's AGENTS.md Feature Configuration (messaging-provider, outbox-enabled, data-provider, rop-enabled) and batches all remaining questions into a single interview turn. - Validation and guardrails: Verifies the build, confirms subscriber discovery via AddSubscribersUsing<T>(), and enforces rules such as skipping repositories for event-data-sync scenarios. - Use Case: You need a new subscriber for the products.product.modified event that replicates data into a local store. The Skill gathers the subject and scenario, invokes the contract, subscriber, and test skills in order, and finishes with a validated build. ## Quick Start Ask the assistant to add a new subscriber for a given event or command subject to your CoreEx Subscribe host and specify whether it is a command, event-data-sync, or business-process scenario.
