aw-spec-cli 0.1.0 → 0.1.2

package/assets/docs/architecture/testing.md

@@ -0,0 +1,55 @@
+# Testing Standards
+
+> Pure technology (domain-agnostic) — domain additions in [[testing.domain]]. Commands: `/aw-spec-tasks`, `/aw-spec-implement`.
+
+## Test-first engineering
+
+- Generated tests follow Test-First Engineering and **MUST fail before** the production
+  change is in place.
+- Any change to an aggregate invariant, endpoint contract, or error code **MUST** include
+  the corresponding test update **in the same commit**.
+
+## Unit test conventions
+
+- Unit tests are required for **every** aggregate behavior, value object, and specification.
+- Tests are **deterministic** — time, randomness, and IDs are injected
+  (use the framework-provided `IClock` / `IGuidGenerator`). Never `DateTime.UtcNow` /
+  `Guid.NewGuid()` in the system under test.
+- Tests **MUST NOT** reach into module internals; they exercise the public endpoint or
+  `IMediator` surface.
+
+## Handler tests
+
+Required for **every** Command/Query handler and MUST cover:
+
+- happy path
+- validation failure
+- not-found
+- (for writes) concurrency conflict
+
+## Integration testing
+
+- Required for **every** endpoint; run against **PostgreSQL via Testcontainers** or Aspire.
+- Test database engine: Testcontainers PostgreSQL for integration; in-memory fixtures for
+  unit tests.
+
+## Testcontainers usage
+
+- Integration and contract tests spin up real PostgreSQL (and other backing services)
+  via Testcontainers / Aspire — no faked persistence in integration tests.
+
+## Test data hygiene
+
+- Tests use a **shared fixture library** rather than inlining fabricated data.
+- Production data MUST NOT be used in development, test, demo, or shared CI.
+  (Domain specifics — synthetic fixtures + terminology sentinels — in [[testing.domain]].)
+
+## Coverage rules
+
+- Minimum **85% line coverage** on Application + Domain.
+- **100%** on aggregate behaviors and value objects.
+- Code coverage on changed files must meet the threshold (CI gate).
+
+## Related
+
+- [[domain-driven-design]] · [[persistence]] · [[testing.domain]]

package/assets/docs/architecture/vertical-slices.md

@@ -0,0 +1,201 @@
+# Vertical Slice Standards
+
+> Pure technology (domain-agnostic) — domain additions in [[vertical-slices.domain]]. Commands: `/aw-spec-plan`, `/aw-spec-tasks`, `/aw-spec-implement`.
+
+## Feature organization
+
+- Each feature is a **self-contained vertical slice**: Command/Query, Handler, Endpoint,
+  Validator co-located in **one folder**.
+- No horizontal "Services/Managers" layers spanning slices.
+
+## Folder structure (per module)
+
+```
+<Module>/
+  Domain/
+    <Aggregate>.cs
+    <ChildEntity>.cs
+    <ValueObject>.cs
+    <Aggregate>Id.cs            [ValueObject<Guid>] partial struct
+    Events/                     DomainEventBase descendants
+    Specifications/
+  Persistence/<Aggregate>Configuration.cs
+  Features/<FeatureName>/       Command/Query + Handler + Endpoint + Validator
+  Interop/                      external-protocol adapters (see [[vertical-slices.domain]])
+  Shared/                       module-public DTOs + ToDto extensions
+```
+
+## Endpoint conventions
+
+- One endpoint **per file**. Endpoints inherit `SecureFastEndpoint<TRequest, TResponse>`.
+- Kebab-case routes; resources are plural nouns; verbs map to intent
+  (POST create, GET list/fetch, PUT full update, PATCH partial update, DELETE logical delete).
+- GUID route ids **MUST** use the `:guid` constraint.
+- Tagged via `Options(o => o.WithTags("NN - <Module> - (FastEndpoints)"))` and **MUST**
+  provide a `Summary`.
+- HTTP request classes are declared **inside the same file as the Endpoint** and contain
+  **primitive types only**.
+- Endpoints **MUST NOT** swallow exceptions — the central exception handler owns the contract.
+- See [[authorization]] for security cache policy on endpoints.
+
+## Validator placement
+
+- Validators live in the **feature folder** alongside the Command/Query they validate.
+- Validators check **request shape only**; aggregate invariants are enforced in the Domain.
+
+## DTO placement (immutable contracts)
+
+- DTOs live in `{Module}/Shared/` and are mapped with **hand-written** `ToDto()` /
+  `ToDtoList()` extension methods. AutoMapper-style reflection mappers are FORBIDDEN.
+- `record EntityDto { public required Guid Id { get; init; } ... }` — no setters;
+  required init for non-nullable members.
+- Every DTO **MUST** include a base64 `RowVersionBase64` when the aggregate implements
+  `IConcurrencyTracked`.
+- Paged results **MUST** use the standard `PagedResult<T>` shape
+  (`Items, TotalCount, PageNumber, PageSize`, computed `TotalPages`) with required init props.
+
+## Specification placement
+
+- Query composition lives in the **Domain**, under `{Module}/Domain/Specifications/`.
+  See [[persistence]] for specification rules.
+
+## Canonical example (agent reference — `<SampleProjectName>` sample)
+
+A complete slice: Endpoint (+ request class in the same file), Validator, DTO, and mapping.
+
+```csharp
+// <SampleProjectName>.Service/Projects/Features/CreateProject/CreateProjectEndpoint.cs
+public class CreateProjectEndpoint(IMediator _mediator)
+    : SecureFastEndpoint<CreateProjectRequest, ProjectDto>
+{
+    public override void Configure()
+    {
+        Post("/projects");                                  // kebab-case, plural noun
+        Summary(s => s.Summary = "Create a new project");
+        Options(o => o.WithTags("02 - Project - (FastEndpoints)"));
+    }
+
+    protected override SecurityCachePolicy GetSecurityCachePolicy() => new()
+    {
+        SecurityLevel = SecurityLevel.Internal,
+        CachePolicy = CachePolicy.NoStore                   // mutating endpoint
+    };
+
+    protected override async Task<Result<ProjectDto>> ExecuteAsync(
+        CreateProjectRequest req, CancellationToken ct)
+    {
+        var result = await _mediator.Send(new CreateProjectCommand(   // IMediator only
+            req.Code, req.Name, req.Description, req.StartDate, req.EndDate, req.OwnerId), ct);
+
+        if (result.IsSuccess && !string.IsNullOrWhiteSpace(result.Value?.RowVersionBase64))
+            HttpContext.Response.SetETagFromBase64(result.Value!.RowVersionBase64);
+        return result;
+    }
+}
+
+// Request lives in the SAME file — primitive types only
+public class CreateProjectRequest
+{
+    public string Code { get; set; } = string.Empty;
+    public string Name { get; set; } = string.Empty;
+    public string? Description { get; set; }
+    public DateOnly StartDate { get; set; }
+    public DateOnly? EndDate { get; set; }
+    public Guid? OwnerId { get; set; }
+}
+```
+
+```csharp
+// .../CreateProject/CreateProjectValidator.cs — request shape only
+public class CreateProjectValidator : AbstractValidator<CreateProjectCommand>
+{
+    public CreateProjectValidator()
+    {
+        RuleFor(x => x.Code).NotEmpty().MaximumLength(20).Matches(@"^[A-Z0-9\-]+$");
+        RuleFor(x => x.Name).NotEmpty().MaximumLength(200);
+        RuleFor(x => x.EndDate)
+            .GreaterThanOrEqualTo(x => x.StartDate).When(x => x.EndDate.HasValue);
+    }
+}
+```
+
+```csharp
+// {Module}/Shared/ProjectDto.cs — includes RowVersionBase64 (IConcurrencyTracked)
+public record ProjectDto
+{
+    public Guid Id { get; set; }
+    public string Code { get; set; } = string.Empty;
+    public string Name { get; set; } = string.Empty;
+    public string Status { get; set; } = string.Empty;
+    public Guid? OwnerId { get; set; }
+    public List<ProjectTaskDto> Tasks { get; set; } = new();
+    public string RowVersionBase64 { get; set; } = string.Empty;
+}
+
+// {Module}/Shared/ProjectMappingExtensions.cs — hand-written, zero reflection
+public static class ProjectMappingExtensions
+{
+    public static ProjectDto ToDto(this Project e) => new()
+    {
+        Id = e.Id.Value, Code = e.Code.Value, Name = e.Name,
+        Status = e.Status.ToString(), OwnerId = e.OwnerId?.Value,
+        Tasks = e.Tasks.Select(t => t.ToDto()).ToList(),
+        RowVersionBase64 = e.RowVersion is { Length: > 0 } rv
+            ? Convert.ToBase64String(rv) : string.Empty
+    };
+
+    public static List<ProjectDto> ToDtoList(this IEnumerable<Project> es)
+        => es.Select(e => e.ToDto()).ToList();
+}
+```
+
+Sub-resource endpoint for a distinct operation on a child — nested route, multiple route
+params, `EmptyResponse` when there is no body to return:
+
+```csharp
+// .../Features/AssignTask/AssignTaskEndpoint.cs
+public class AssignTaskEndpoint(IMediator _mediator)
+    : SecureFastEndpoint<AssignTaskRequest, EmptyResponse>
+{
+    public override void Configure()
+    {
+        Put("/projects/{projectId:guid}/tasks/{taskId:guid}/assignee");   // sub-resource
+        Summary(s => s.Summary = "Assign a task to a TaskUser");
+        Options(o => o.WithTags("02 - Project - (FastEndpoints)"));
+    }
+
+    protected override SecurityCachePolicy GetSecurityCachePolicy() => new()
+    { SecurityLevel = SecurityLevel.Internal, CachePolicy = CachePolicy.NoStore };
+
+    protected override async Task<Result<EmptyResponse>> ExecuteAsync(
+        AssignTaskRequest req, CancellationToken ct)
+    {
+        var projectId = Route<Guid>("projectId");
+        var taskId = Route<Guid>("taskId");
+        var result = await _mediator.Send(new AssignTaskCommand(projectId, taskId, req.AssigneeId), ct);
+        return result.IsSuccess
+            ? Result<EmptyResponse>.Ok(new EmptyResponse())
+            : Result<EmptyResponse>.Failure([.. result.Errors]);
+    }
+}
+
+public class AssignTaskRequest { public Guid AssigneeId { get; set; } }
+```
+
+Standard `PagedResult<T>` contract (required init props, computed `TotalPages`):
+
+```csharp
+// {Module}/Common/PagedResult.cs
+public sealed class PagedResult<T>
+{
+    public required IReadOnlyList<T> Items { get; init; }
+    public required int TotalCount { get; init; }
+    public required int PageNumber { get; init; }
+    public required int PageSize { get; init; }
+    public int TotalPages => (int)Math.Ceiling((double)TotalCount / PageSize);
+}
+```
+
+## Related
+
+- [[clean-architecture]] · [[cqrs]] · [[persistence]] · [[authorization]] · [[vertical-slices.domain]]

package/assets/docs/command.txt

@@ -0,0 +1,295 @@
+================================================================================
+AW-SPEC COMMAND SHEET — Feature: Patient Registration  (Patient / RegisterPatient)
+================================================================================
+Run these in order, one per turn, from /aw-spec-specify to /aw-spec-implement.
+All six numbered steps are REQUIRED for this feature — clarify and analyze are
+correctness gates, not optional extras (see their sections for why).
+
+CONVENTIONS USED BELOW
+- @paths are Claude Code file mentions; they are inlined as context. Paths are
+  relative to the workspace root (e:\Work\Company\Project), so they start with `docs/...`.
+- "MANUAL TEXT" = the plain prompt you type as part of the command.
+- The spec folder convention is specs/<Aggregate>/<Feature>; starting the feature
+  description with the token `Patient/RegisterPatient` makes /aw-spec-specify create
+  specs/Patient/RegisterPatient/ and pin it in .aw-spec/feature.json. Every later
+  command (clarify/plan/tasks/analyze/implement) auto-resolves that folder from
+  feature.json — you do NOT pass the aggregate/feature token again.
+- The constitution (.aw-spec/memory/constitution.md) AND the domain-agnostic technical
+  standards are AUTO-LOADED by each command (see each SKILL.md) — you
+  do NOT pass those with @.
+- The DOMAIN-SPECIFIC files shown per step come from the active domain's comandrulemap.md
+  (active domain = .aw-spec/domain.json, set via /aw-spec-select-domain). Each command offers
+  them in a selection box (Select all / Pick a subset / None); the @ mentions below are an
+  equivalent, OPTIONAL shortcut and are always loaded in addition to the auto-loaded set.
+
+INTEROPERABILITY SCOPE FOR THIS FEATURE
+  Patient registration is an interoperability-heavy feature. It MUST support:
+   - Inbound HL7 v2 ADT^A04 (Register a Patient) via an Interop/Hl7v2 adapter that
+     converts the message to the RegisterPatientCommand (never writes to the aggregate
+     directly), over MLLP, with ACK handling.
+   - Outbound ADT emission on PatientRegisteredEvent (egress adapter).
+   - External FHIR R4 Patient projection + PIX/PDQ identity cross-reference.
+  Therefore docs/domainspecs/healthcare/hl7.md and the eventing docs are part of the context from
+  specify through implement.
+
+SETUP (one-time per project) — set the active domain
+  /aw-spec-select-domain              (lists docs/domainspecs/ folders; writes .aw-spec/domain.json)
+  /aw-spec-select-domain healthcare   (or set it directly)
+  -> For this demo the domain is `healthcare` (already set). If the domain is unset or its
+     comandrulemap.md is missing, every command first asks "Continue without domain rules?
+     (Continue / Exit)" before running.
+
+PREREQUISITE (one-time, only if the constitution has not been ratified yet)
+  /aw-spec-constitution @docs/healthcare-constitution.md @docs/domainspecs/healthcare/domain-requirements.md
+  -> docs/technology-constitution.md auto-loads (technology base); pass only the domain addenda.
+  -> Ratifies .aw-spec/memory/constitution.md. Not part of the per-feature loop.
+
+
+================================================================================
+STEP 1 — /aw-spec-specify   (create the feature spec)
+================================================================================
+PURPOSE
+  Create specs/Patient/RegisterPatient/spec.md (WHAT/WHY, no implementation detail)
+  and pin the folder in .aw-spec/feature.json. A git feature branch is created by the
+  before_specify hook.
+
+CONTEXT FILES TO ADD
+  docs/domainspecs/healthcare/domain-requirements.md          (bounded contexts: Patient aggregates)
+  docs/domainspecs/healthcare/clinical-terms.md             (MRN, Encounter, Coverage, ...)
+  docs/domainspecs/healthcare/integration-terms.md          (FHIR, HL7, PIX/PDQ, ATNA, ADT)
+  docs/domainspecs/healthcare/domain-driven-design.domain.md  (Patient invariants)
+  docs/domainspecs/healthcare/fhir.md                          (Patient FHIR projection)
+  docs/domainspecs/healthcare/hl7.md                           (HL7 v2 ADT ingestion/egress)  <-- HL7
+  docs/domainspecs/healthcare/dicom.md                         (imaging identifiers; optional for registration)
+  docs/domainspecs/healthcare/terminology.md                   (coded fields)
+  docs/domainspecs/healthcare/hipaa.md                          (PHI / minimum-necessary)
+  docs/domainspecs/healthcare/consent.md                        (Consent at registration)
+  docs/domainspecs/healthcare/data-classification.domain.md   (PHI/PII categories)
+  docs/domainspecs/healthcare/ai-rules.domain.md              (PHI masking, no invented codes)
+
+COMMAND (copy-paste, single line)
+/aw-spec-specify Patient/RegisterPatient Register a new patient into the master patient index. Capture demographics (legal HumanName, date of birth, administrative sex, contact points, address) and assign a tenant-unique MRN. Invariants: MRN is unique per tenant; date-of-birth must not be in the future; minimum-necessary projection by role/scope. Interoperability: inbound HL7 v2 ADT^A04 (Register a Patient) messages MUST be ingested through an Interop/Hl7v2 adapter that converts to the RegisterPatientCommand (no direct aggregate writes) over MLLP with ACK handling, and an outbound ADT emitter fires on PatientRegisteredEvent; also expose an external FHIR R4 Patient projection and PIX/PDQ identity cross-reference. Surfaces: internal REST POST /patients returning the created Patient, the FHIR R4 Patient endpoint, and the HL7 v2 ADT ingress channel. Every PHI read/write must produce an ATNA audit record. Out of scope: patient merge, portal self-registration. @docs/domainspecs/healthcare/domain-requirements.md @docs/domainspecs/healthcare/clinical-terms.md @docs/domainspecs/healthcare/integration-terms.md @docs/domainspecs/healthcare/domain-driven-design.domain.md @docs/domainspecs/healthcare/fhir.md @docs/domainspecs/healthcare/hl7.md @docs/domainspecs/healthcare/dicom.md @docs/domainspecs/healthcare/terminology.md @docs/domainspecs/healthcare/hipaa.md @docs/domainspecs/healthcare/consent.md @docs/domainspecs/healthcare/data-classification.domain.md @docs/domainspecs/healthcare/ai-rules.domain.md
+
+MANUAL TEXT (the prompt portion, for reference)
+  Patient/RegisterPatient Register a new patient into the master patient index. Capture
+  demographics (legal HumanName, date of birth, administrative sex, contact points,
+  address) and assign a tenant-unique MRN. Optionally link an insurance Coverage and
+  capture initial patient Consent. Invariants: MRN is unique per tenant; date-of-birth
+  must not be in the future; minimum-necessary projection by role/scope.
+  Interoperability: inbound HL7 v2 ADT^A04 (Register a Patient) messages MUST be ingested
+  through an Interop/Hl7v2 adapter that converts to the RegisterPatientCommand (no direct
+  aggregate writes) over MLLP with ACK handling, and an outbound ADT emitter fires on
+  PatientRegisteredEvent; also expose an external FHIR R4 Patient projection and PIX/PDQ
+  identity cross-reference. Surfaces: internal REST POST /patients returning the created
+  PatientDto with an ETag, the FHIR R4 Patient endpoint, and the HL7 v2 ADT ingress
+  channel. Every PHI read/write must produce an ATNA audit record. Out of scope: patient
+  merge, portal self-registration.
+
+NOTES
+  - The leading `Patient/RegisterPatient` token sets the spec folder; keep PascalCase.
+  - Expect output: SPEC_FILE = specs/Patient/RegisterPatient/spec.md.
+
+
+================================================================================
+STEP 2 — /aw-spec-clarify   (REQUIRED — feature-correctness gate)
+================================================================================
+WHY THIS MATTERS (do not skip)
+  Clarify finds underspecified areas and asks up to 5 targeted questions, then writes the
+  answers back into spec.md. Building plan/tasks/code on an ambiguous spec is the most
+  expensive mistake in the pipeline — for a PHI + HL7 feature the ambiguities have real
+  cost. Resolve at least:
+   - HL7 scope: only ADT^A04, or also A28 (add person) / A31 (update) / A08 (update info)?
+     Which MSH sending/receiving apps? MLLP vs file drop? ACK mode (AA/AE/AR) and NAK on
+     duplicate MRN?
+   - Identity: who assigns the MRN (this system vs source)? PIX/PDQ matching rules and
+     duplicate/merge-candidate handling on inbound ADT.
+   - Consent: is Consent mandatory at registration or optional? purpose-of-use default.
+   - Demographics: required vs optional fields; terminology bindings (administrative sex,
+     marital status); multiple-birth/aliases.
+   - Coverage: required at registration or deferred.
+  Re-run until no high-impact (scope/PHI/interop) ambiguity remains.
+
+CONTEXT FILES TO ADD
+  docs/domainspecs/healthcare/domain-driven-design.domain.md
+  docs/domainspecs/healthcare/hl7.md                          (HL7 ADT clarifications)  <-- HL7
+  docs/domainspecs/healthcare/hipaa.md
+  docs/domainspecs/healthcare/consent.md
+  docs/domainspecs/healthcare/clinical-terms.md
+  docs/domainspecs/healthcare/integration-terms.md
+
+COMMAND
+/aw-spec-clarify @docs/domainspecs/healthcare/domain-driven-design.domain.md @docs/domainspecs/healthcare/hl7.md @docs/domainspecs/healthcare/hipaa.md @docs/domainspecs/healthcare/consent.md @docs/domainspecs/healthcare/clinical-terms.md @docs/domainspecs/healthcare/integration-terms.md
+
+MANUAL TEXT
+  (none — answer the questions it asks; the answers are written back into spec.md)
+
+
+================================================================================
+STEP 3 — /aw-spec-plan   (create the implementation plan / design)
+================================================================================
+PURPOSE
+  Produce plan.md (+ research/data-model/contracts) under specs/Patient/RegisterPatient/.
+  This is where the engineering standards matter most — load the architecture stack,
+  the HL7 adapter rules, and the eventing rules for inbound feeds.
+
+CONTEXT FILES TO ADD
+  Architecture (technology):
+    docs/architecture/folder-structure.md
+    docs/architecture/clean-architecture.md
+    docs/architecture/modular-monolith.md
+    docs/architecture/cqrs.md
+    docs/architecture/vertical-slices.md
+    docs/architecture/persistence.md
+    docs/architecture/eventing.md
+    docs/domainspecs/healthcare/eventing.domain.md       (HL7/FHIR inbound feeds)  <-- HL7
+    docs/architecture/testing.md
+  Domain (healthcare, this slice):
+    docs/domain/domain-driven-design.md
+    docs/domainspecs/healthcare/domain-driven-design.domain.md
+    docs/domainspecs/healthcare/fhir.md
+    docs/domainspecs/healthcare/hl7.md                          (HL7 v2 adapter pattern)  <-- HL7
+    docs/domainspecs/healthcare/dicom.md                        (imaging identifiers; optional for registration)
+    docs/domainspecs/healthcare/terminology.md
+    docs/domainspecs/healthcare/hipaa.md
+    docs/domainspecs/healthcare/consent.md
+  Security:
+    docs/security/authorization.md  + .domain.md
+    docs/security/auditing.md        + .domain.md
+    docs/domainspecs/healthcare/data-classification.domain.md
+  Governance + AI rules:
+    docs/governance/coding-standards.md  + .domain.md
+    docs/glossary/ai-rules.md            + .domain.md
+
+COMMAND (copy-paste, single line)
+/aw-spec-plan Implement RegisterPatient as a complete vertical slice in the Patients module following the loaded standards: Patient aggregate root (Vogen PatientId, MRN value object, HumanName/Address/ContactPoint value objects), RegisterPatientCommand + handler (transaction + PatientRegisteredEvent), SecureFastEndpoint POST /patients with ETag, PatientDto + hand-written ToDto, EF configuration + migration, FHIR R4 Patient projector, and the PHI-access audit behavior. Interop: an Interop/Hl7v2 inbound adapter that parses ADT^A04 and dispatches RegisterPatientCommand via IMediator (no direct aggregate writes), MLLP transport + ACK, and an outbound ADT emitter subscribed to PatientRegisteredEvent; plan PIX/PDQ identity cross-reference. Use AppWeaver.Mediator/Repository/ServiceDefaults per the docs; PostgreSQL prod / SQLite dev; no MediatR/AutoMapper. @docs/architecture/folder-structure.md @docs/architecture/clean-architecture.md @docs/architecture/modular-monolith.md @docs/architecture/cqrs.md @docs/architecture/vertical-slices.md @docs/architecture/persistence.md @docs/architecture/eventing.md @docs/domainspecs/healthcare/eventing.domain.md @docs/architecture/testing.md @docs/domain/domain-driven-design.md @docs/domainspecs/healthcare/domain-driven-design.domain.md @docs/domainspecs/healthcare/fhir.md @docs/domainspecs/healthcare/hl7.md @docs/domainspecs/healthcare/dicom.md @docs/domainspecs/healthcare/terminology.md @docs/domainspecs/healthcare/hipaa.md @docs/domainspecs/healthcare/consent.md @docs/security/authorization.md @docs/domainspecs/healthcare/authorization.domain.md @docs/security/auditing.md @docs/domainspecs/healthcare/auditing.domain.md @docs/domainspecs/healthcare/data-classification.domain.md @docs/governance/coding-standards.md @docs/domainspecs/healthcare/coding-standards.domain.md @docs/glossary/ai-rules.md @docs/domainspecs/healthcare/ai-rules.domain.md
+
+MANUAL TEXT (the prompt portion, for reference)
+  Implement RegisterPatient as a complete vertical slice in the Patients module following
+  the loaded standards: Patient aggregate root (Vogen PatientId, MRN value object,
+  HumanName/Address/ContactPoint value objects), RegisterPatientCommand + handler
+  (transaction + PatientRegisteredEvent), SecureFastEndpoint POST /patients with ETag,
+  PatientDto + hand-written ToDto, EF configuration + migration, FHIR R4 Patient projector,
+  and the PHI-access audit behavior. Interop: an Interop/Hl7v2 inbound adapter that parses
+  ADT^A04 and dispatches RegisterPatientCommand via IMediator (no direct aggregate writes),
+  MLLP transport + ACK, and an outbound ADT emitter subscribed to PatientRegisteredEvent;
+  plan PIX/PDQ identity cross-reference. Use AppWeaver.Mediator/Repository/ServiceDefaults
+  per the docs; PostgreSQL prod / SQLite dev; no MediatR/AutoMapper.
+
+NOTES
+  - No aggregate/feature token here — the folder is resolved from feature.json.
+
+
+================================================================================
+STEP 4 — /aw-spec-tasks   (generate the dependency-ordered task list)
+================================================================================
+PURPOSE
+  Produce tasks.md from plan.md under specs/Patient/RegisterPatient/.
+
+CONTEXT FILES TO ADD
+  docs/architecture/folder-structure.md
+  docs/architecture/vertical-slices.md   (+ .domain.md)
+  docs/architecture/cqrs.md               (+ .domain.md)
+  docs/architecture/persistence.md        (+ .domain.md)
+  docs/architecture/testing.md            (+ .domain.md)
+  docs/architecture/eventing.md           (+ .domain.md)
+  docs/domainspecs/healthcare/domain-driven-design.domain.md
+  docs/domainspecs/healthcare/fhir.md
+  docs/domainspecs/healthcare/hl7.md                       (HL7 adapter tasks)  <-- HL7
+  docs/security/authorization.md          (+ .domain.md)
+  docs/security/auditing.md               (+ .domain.md)
+  docs/governance/coding-standards.md     (+ .domain.md)
+  docs/glossary/ai-rules.md               (+ .domain.md)
+
+COMMAND (copy-paste, single line)
+/aw-spec-tasks Break the plan into ordered, testable tasks for the RegisterPatient slice: value objects + tests, Patient aggregate + invariant tests, EF config + migration, RegisterPatientCommand/Validator/Handler + handler tests (happy/validation/not-found/conflict), SecureFastEndpoint + integration test, FHIR Patient projector + round-trip test, HL7 v2 ADT^A04 inbound parser + outbound emitter with HL7 conformance tests against an internal corpus, PatientRegisteredEvent + publish, PHI-audit wiring. Tests precede implementation. @docs/architecture/folder-structure.md @docs/architecture/vertical-slices.md @docs/domainspecs/healthcare/vertical-slices.domain.md @docs/architecture/cqrs.md @docs/domainspecs/healthcare/cqrs.domain.md @docs/architecture/persistence.md @docs/domainspecs/healthcare/persistence.domain.md @docs/architecture/testing.md @docs/domainspecs/healthcare/testing.domain.md @docs/architecture/eventing.md @docs/domainspecs/healthcare/eventing.domain.md @docs/domainspecs/healthcare/domain-driven-design.domain.md @docs/domainspecs/healthcare/fhir.md @docs/domainspecs/healthcare/hl7.md @docs/security/authorization.md @docs/domainspecs/healthcare/authorization.domain.md @docs/security/auditing.md @docs/domainspecs/healthcare/auditing.domain.md @docs/governance/coding-standards.md @docs/domainspecs/healthcare/coding-standards.domain.md @docs/glossary/ai-rules.md @docs/domainspecs/healthcare/ai-rules.domain.md
+
+MANUAL TEXT (the prompt portion, for reference)
+  Break the plan into ordered, testable tasks for the RegisterPatient slice: value objects
+  + tests, Patient aggregate + invariant tests, EF config + migration,
+  RegisterPatientCommand/Validator/Handler + handler tests
+  (happy/validation/not-found/conflict), SecureFastEndpoint + integration test, FHIR
+  Patient projector + round-trip test, HL7 v2 ADT^A04 inbound parser + outbound emitter
+  with HL7 conformance tests against an internal corpus, PatientRegisteredEvent + publish,
+  PHI-audit wiring. Tests precede implementation.
+
+
+================================================================================
+STEP 5 — /aw-spec-analyze   (REQUIRED — cross-artifact correctness gate)
+================================================================================
+WHY THIS MATTERS (do not skip)
+  Analyze is a non-destructive consistency/quality check across spec.md, plan.md, and
+  tasks.md, run AFTER tasks and BEFORE implement. It is the last gate before code, and for
+  a regulated, interoperable feature it catches exactly the failures that are most costly
+  after implementation:
+   - Requirements in the spec with no covering task (e.g. ADT^A04 ingest, PIX/PDQ, Consent
+     capture, audit on every PHI write).
+   - Tasks with no basis in the spec (scope creep).
+   - Constitution NON-NEGOTIABLE gaps: missing ATNA audit task, hard-delete instead of
+     soft-delete, missing ETag/If-Match concurrency, PHI in logs, free-text where a coded
+     value object is required, a second FHIR write path, banned packages.
+   - Terminology / naming drift between artifacts.
+  Fix everything it flags by amending spec/plan/tasks, then re-run until clean.
+
+CONTEXT FILES TO ADD
+  docs/domainspecs/healthcare/hl7.md                       (verify HL7 coverage)  <-- HL7
+  docs/domainspecs/healthcare/hipaa.md
+  docs/domainspecs/healthcare/auditing.domain.md
+  docs/governance/coding-standards.md     (+ .domain.md)
+  docs/domainspecs/healthcare/ai-rules.domain.md
+
+COMMAND
+/aw-spec-analyze @docs/domainspecs/healthcare/hl7.md @docs/domainspecs/healthcare/hipaa.md @docs/domainspecs/healthcare/auditing.domain.md @docs/governance/coding-standards.md @docs/domainspecs/healthcare/coding-standards.domain.md @docs/domainspecs/healthcare/ai-rules.domain.md
+
+MANUAL TEXT
+  (none — review the report, then amend spec/plan/tasks for any finding and re-run)
+
+
+================================================================================
+STEP 6 — /aw-spec-implement   (execute the tasks / write the code)
+================================================================================
+PURPOSE
+  Execute tasks.md and produce the actual source under src/ following the standards.
+  Add the full implementation context: tasks-set + HL7 + dependency/versioning +
+  FHIR/terminology + data-classification/zero-trust.
+
+CONTEXT FILES TO ADD
+  (everything from STEP 4) PLUS:
+    docs/domainspecs/healthcare/hl7.md                      (already in step 4 — keep)  <-- HL7
+    docs/governance/dependency-policy.md   (+ .domain.md)
+    docs/governance/api-versioning.md      (+ .domain.md)
+    docs/domainspecs/healthcare/terminology.md
+    docs/security/data-classification.md    (+ .domain.md)
+    docs/security/zero-trust.md             (+ .domain.md)
+
+COMMAND (copy-paste, single line)
+/aw-spec-implement Implement the RegisterPatient tasks exactly per the loaded standards. Generate the complete vertical slice (Domain/Persistence/Features/Shared), the Interop/Hl7v2 ADT^A04 inbound adapter + outbound ADT emitter (MLLP + ACK, no direct aggregate writes), the FHIR R4 Patient projector, unit + integration + FHIR-validator + HL7-conformance tests, and the EF migration. Honor every NON-NEGOTIABLE: Result pattern, ETag/If-Match concurrency, soft-delete, ATNA audit, minimum-necessary, no PHI in logs, coded value objects, inbound feeds via adapters only, no banned packages. Do not run migrations against shared environments. @docs/architecture/folder-structure.md @docs/architecture/vertical-slices.md @docs/domainspecs/healthcare/vertical-slices.domain.md @docs/architecture/cqrs.md @docs/domainspecs/healthcare/cqrs.domain.md @docs/architecture/persistence.md @docs/domainspecs/healthcare/persistence.domain.md @docs/architecture/testing.md @docs/domainspecs/healthcare/testing.domain.md @docs/architecture/eventing.md @docs/domainspecs/healthcare/eventing.domain.md @docs/domain/domain-driven-design.md @docs/domainspecs/healthcare/domain-driven-design.domain.md @docs/domainspecs/healthcare/fhir.md @docs/domainspecs/healthcare/hl7.md @docs/domainspecs/healthcare/terminology.md @docs/domainspecs/healthcare/hipaa.md @docs/domainspecs/healthcare/consent.md @docs/security/authorization.md @docs/domainspecs/healthcare/authorization.domain.md @docs/security/auditing.md @docs/domainspecs/healthcare/auditing.domain.md @docs/security/data-classification.md @docs/domainspecs/healthcare/data-classification.domain.md @docs/security/zero-trust.md @docs/domainspecs/healthcare/zero-trust.domain.md @docs/governance/coding-standards.md @docs/domainspecs/healthcare/coding-standards.domain.md @docs/governance/dependency-policy.md @docs/domainspecs/healthcare/dependency-policy.domain.md @docs/governance/api-versioning.md @docs/domainspecs/healthcare/api-versioning.domain.md @docs/glossary/ai-rules.md @docs/domainspecs/healthcare/ai-rules.domain.md
+
+MANUAL TEXT (the prompt portion, for reference)
+  Implement the RegisterPatient tasks exactly per the loaded standards. Generate the
+  complete vertical slice (Domain/Persistence/Features/Shared), the Interop/Hl7v2 ADT^A04
+  inbound adapter + outbound ADT emitter (MLLP + ACK, no direct aggregate writes), the
+  FHIR R4 Patient projector, unit + integration + FHIR-validator + HL7-conformance tests,
+  and the EF migration. Honor every NON-NEGOTIABLE: Result pattern, ETag/If-Match
+  concurrency, soft-delete, ATNA audit, minimum-necessary, no PHI in logs, coded value
+  objects, inbound feeds via adapters only, no banned packages. Do not run migrations
+  against shared environments.
+
+
+================================================================================
+QUICK REFERENCE — order of operations (all required for this feature)
+================================================================================
+  (0) /aw-spec-select-domain  ... one-time: set active domain (healthcare) -> .aw-spec/domain.json
+ (0b) /aw-spec-constitution   ... one-time, if not yet ratified
+   1. /aw-spec-specify        ... Patient/RegisterPatient + domain/glossary + HL7 context
+   2. /aw-spec-clarify        ... correctness gate: resolve HL7/PHI/identity ambiguities
+   3. /aw-spec-plan           ... architecture + domain + HL7/eventing + security + governance
+   4. /aw-spec-tasks          ... tasks-set + HL7 adapter/conformance tasks
+   5. /aw-spec-analyze        ... correctness gate: spec<->plan<->tasks + NON-NEGOTIABLE coverage
+   6. /aw-spec-implement      ... full build: slice + HL7 adapters + FHIR + tests + migration
+
+All steps after /aw-spec-specify auto-resolve specs/Patient/RegisterPatient/ from
+.aw-spec/feature.json — do not repeat the Patient/RegisterPatient token.
+
+HL7 v2 is threaded through every step (docs/domainspecs/healthcare/hl7.md + docs/domainspecs/healthcare/eventing.domain.md) because inbound
+ADT^A04 ingestion and outbound ADT emission are first-class surfaces of this feature, not an
+afterthought — interoperability is a NON-NEGOTIABLE constitution principle (XIV).