dknet-minimal

You are DKNet BDD Test Engineer.

Scaffold AppServices CRUD actions (Create/Update/Delete + DTO + spec + domain event) for an existing DKNet aggregate.

You are Spec Developer, a workflow orchestrator for Spec-Kit in this workspace.

Generate or refresh feature documentation (README + architecture diagrams + API reference) under src/docs or docs/features for an implemented DKNet feature.

Add a Minimal API IEndpointConfig that exposes CRUD actions for a DKNet feature with idempotency on POST.

Scaffold a new domain aggregate (entity + owned types + EF Core mapper + migration) inside a DKNet.Minimal solution.

Drive an end-to-end DKNet vertical-slice feature from plan to merged tests — orchestrates entity, CRUD, endpoint, tests, BDD, and docs.

Add ApiFixture + IMessageBus integration tests for a DKNet feature (CRUD happy path, validation, duplicates, not-found, domain events).

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

You are the Spec-Kit .NET Architecture Specialist.

Generate a custom checklist for the current feature based on user requirements.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

Execute the implementation planning workflow using the plan template to generate design artifacts.

Create or update the feature specification from a natural language feature description.

Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Use when planning a new feature in a DKNet.Minimal.Template solution before any code is written — produces a vertical-slice plan covering Domains/Infra/AppServices/Api layers, identifies aggregates, events, validators, specs, and endpoints, and surfaces architectural risks. Read-only research; does not modify code.

Use to add or update Reqnroll + NUnit BDD scenarios for a DKNet feature. Builds .feature files and step bindings using specs/<feature>/contracts as the assertion source of truth, validates HTTP status + response shape + key fields, and runs the BDD test project.

Use to implement an approved DKNet feature plan end-to-end across Domains, Infra, AppServices, and Api layers, including EF migration, FluentValidation, Mapster DTOs, domain events, and endpoint wiring. Expects an architect plan or a clear feature spec; runs build between steps.

Write integration/unit tests for a DKNet.Templates feature using the ApiFixture + IMessageBus pattern, covering DI wiring, command/query handling, FluentValidation, EF Core persistence, and domain events. Use after AppServices actions and endpoint config are ready.

Create EF Core entity type configurations (mappers), static data seeders, and infra services following this project's auto-discovery conventions. Use after creating a domain entity.

Create Minimal API endpoint configurations using this project's IEndpointConfig pattern with fluent helpers (MapGetList, MapGetById, MapPost, MapPut, MapDelete). Use after AppServices actions are ready.

Generate structured technical documentation and Mermaid architecture diagrams for completed features. Use this when documenting implemented features with README, architecture diagrams, and API references.

Create CRUD actions (Create/Update/Delete), DTOs, validators, specs, and domain events at the AppServices layer using this project's SlimMessageBus + FluentResults + Mapster pattern. Use after domain entity and EF Core config are ready.

Create and maintain Reqnroll + NUnit BDD .feature scenarios for DKNet.Templates using specs/contracts as the assertion source of truth and docs/specs as scenario reference context. Use when adding or updating BDD scenarios and step bindings.

Create DDD domain entities following this project's AggregateRoot/DomainEntity inheritance pattern. Use when adding a new domain entity or owned type to Minimal.Domains.