domain-model

Document domain decisions by using ADRs and CONTEXT.md to capture terminology and boundaries. This workflow pairs lightweight documentation with explicit domain language, reducing ambiguity in complex codebases and ensuring code aligns with business context.

Use a domain grill workflow to resolve terminology and cross-context relationships in a monorepo. It interviews decision branches to clarify boundaries, producing context maps that standardize domain understanding across different contexts.

Create ADRs and CONTEXT.md lazily as decisions mature through a stepwise interview process. This lightweight workflow grills decision branches, generating documentation inline to capture cross-context relationships without upfront overhead.

You need ADRs and context maps when managing complex domain boundaries across monorepos or multiple contexts. They clarify decisions and align code with explicit domain language, reducing ambiguity in projects where domain understanding is critical.

The Three-Hat review workflow surfaces concerns by co-creating accessible ADRs and CONTEXT.md files. It reviews domain decisions from multiple perspectives, ensuring terminology and boundaries are validated before documentation is finalized.

This workflow is designed for projects with complex domain boundaries across monorepos or multiple contexts. For simpler projects, the lazy ADR and CONTEXT.md generation may introduce unnecessary overhead without providing significant clarity benefits.