context-scaffold

⚠️ Legacy WildFly context services only. The CQRS scaffolding here — -command-api, -query-api, -domain-event, viewstore + Liquibase, subscriptions-descriptor — is specific to the WildFly-era cpp-context-* stack. Do not copy these patterns into a Spring Boot service. Spring Boot services are layered (Controller → Service → Repository with MapStruct), not CQRS.

For new Spring Boot services, use skills/springboot-service-from-template/. For new HMCTS Marketplace API specs, use skills/springboot-api-from-template/. If a domain genuinely needs CQRS in a new Spring Boot service, that is an ADR-worthy deviation — raise it explicitly rather than importing this skill's patterns.

Context Service Scaffold

Generates boilerplate for new CQRS components within an existing cpp-context-* repository — commands, queries, domain events, viewstore entities, and Liquibase migrations.

When to Use

• User asks to "add a new command", "create a query", "add a domain event"
• User wants to add a new aggregate or entity to the domain
• User needs a new viewstore table with Liquibase migration
• User wants to add event subscription from another context

Component Templates

New Command

When the user wants to add a new command:

1. Command API ({name}-command/{name}-command-api/)

   • RAML definition under src/raml/
   • JSON schema under src/raml/json/schema/
   • Follow existing naming: {context}.command.{verb}-{noun}.json

2. Command Handler ({name}-command/{name}-command-handler/)

   • Handler class implementing the command processing
   • Follow pattern: {Verb}{Noun}CommandHandler.java
   • Must validate invariants via the aggregate
   • Must produce domain events on success

Example command schema naming:

hearing.command.schedule-hearing.json
hearing.command.update-hearing-details.json
hearing.command.cancel-hearing.json

New Query

When the user wants to add a new query:

1. Query API ({name}-query/{name}-query-api/)
   • RAML definition
   • Response JSON schema