domain-context-analyser

Generate a structured domain-context document (.md file with specified sections and placeholders from a user-provided description.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/medmo/conception-eda-wave --skill domain-context-analyser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-context-analyser
Source: https://github.com/medmo/conception-eda-wave/tree/main/.claude/skills/domain-context-analyser
Command: npx skills add https://github.com/medmo/conception-eda-wave --skill domain-context-analyser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill generates a complete domain-context document (context-{nom_du_projet}.md) from a user-provided domain description, ensuring alignment with the EDA domain-context templates and enabling downstream agents to consume a consistent, ready-to-run context.

Core Features & Use Cases

  • Templates-driven generation of the domain context, including Overview, Actors, Business Rules, and Domain Facts.
  • Automatic structuring of sections and placeholders for missing information using the standard [À compléter] convention.
  • Flexible input handling: accepts partial or full domain descriptions and enriches with inferred details.

Quick Start

Provide a concise domain description to generate a file named context-{nom_du_projet}.md.

Frequently Asked Questions about domain-context-analyser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate domain context documentation from a raw domain description?

To generate domain context documentation, provide a raw domain description and the skill outputs a structured Markdown file aligned to EDA templates, covering Actors, Business Rules, and Domain Facts with placeholders for missing data.

What happens if my domain description is missing information for the EDA template?

When your domain description is missing information, the skill infers details where possible and inserts standard [À compléter] placeholders in the generated context file to highlight exactly what needs manual completion.

Can I use a partial domain input to create an EDA domain context file?

Yes, you can use a partial domain input. The skill flexibly accepts incomplete descriptions, automatically enriching them with inferred details to produce a ready-to-run context-{project_name}.md file for downstream design actors.

What sections are included when structuring domain context for event-driven architecture?

Structuring domain context for event-driven architecture includes standard sections like Overview, Actors, Business Rules, and Domain Facts, ensuring downstream agents consume a consistent, ready-to-run context.

What is the best way to automate EDA domain context generation for downstream design?

The best way to automate EDA domain context generation is using a templates-driven approach that processes your domain description and outputs a structured file, ensuring alignment with standard EDA domain-context templates.