ecw-validate-config

ECW Configuration Validation

You are executing the /ecw-validate-config command. Your task is to check the project's ECW configuration completeness and correctness, then output a structured report. Follow the steps below strictly in order.

---

Step 1: Locate Configuration

Check if .claude/ecw/ directory exists. If not, report:

ECW not initialized. Please run /ecw-init first to initialize project configuration.

Then stop.

If the directory exists, read ecw.yml:

cat .claude/ecw/ecw.yml

Parse the paths section to get all configuration paths. If the paths section is missing, fall back to defaults.

---

Step 2: Check ecw.yml

Read .claude/ecw/ecw.yml and check:

2a: Unfilled Placeholders

Search for unreplaced template placeholders:

• project.name still set to "Your Project Name"
• Values containing {...} patterns
• component_types still commented out (only default Service entry)

2b: Language Consistency

• project.language should match files in project root (pom.xml / build.gradle → java)
• scan_patterns values should be appropriate for the declared language

2c: Path Validity

For each path in the paths section, check whether the referenced file/directory exists:

• domain_registry
• path_mappings
• knowledge_root
• knowledge_shared

---

Step 3: Check domain-registry.md

Read the domain registry file (path from ecw.yml or default .claude/ecw/routing/domain-registry.md).

3a: Empty Check

If the file contains no domain blocks (only template header), flag:

• "Domain registry is empty — no business domains registered"

3b: Per-Domain Validation

For each registered domain, extract:

• Domain ID
• Knowledge root path
• Entry document path
• Code root path

Check:

• Does knowledge root exist? — ls {knowledge_root}/ 2>/dev/null
• Does entry document exist? — Check if file at specified path exists
• Does code root exist? — ls {code_root}/ 2>/dev/null
• Any remaining placeholders? — {{...}} or {your_...} patterns