domain-knowledge

To build a shared domain model, you incrementally provide details like entities, attributes, and relationships. The skill structures this input into a queryable format, documenting any gaps with TODO markers to ensure no assumptions are made.

Mapping entity-relationships with incomplete knowledge is handled by a no-assumptions policy. The skill prompts you for missing details and automatically inserts TODO markers in the document, ensuring your domain model remains accurate and clearly highlights gaps.

The best way to document core concepts and lifecycle processes is by capturing them as entities and relationships within a structured domain model. This creates a queryable glossary and enables consistent understanding across all project disciplines.

Yes, you can generate ERDs and process flows directly from your domain knowledge. Once you provide the entities and relationships, the skill visualizes the domain structure into diagrams to clearly communicate the system architecture.

Yes, the approach strictly supports a no-assumptions policy for capturing domain glossaries. Instead of guessing missing details, it actively prompts you with questions and documents uncertainties using TODO markers directly within the domain model.