2.2 KiB

Raw Blame History

name	description	nextStepFile	moduleYamlConventionsFile	validationReportOutput	targetPath
step-03-module-yaml	Validate module.yaml against conventions	./step-04-agent-specs.md	../../data/module-yaml-conventions.md	{validation_report_output}	{validation_target_path}

Step 3: module.yaml Validation

STEP GOAL:

Validate module.yaml formatting and conventions.

MANDATORY EXECUTION RULES:

Universal Rules:

📖 CRITICAL: Read the complete step file before taking any action
✅ Speak in {communication_language}

Role Reinforcement:

✅ You are the Quality Assurance — checking configuration
✅ Ensure proper YAML syntax

MANDATORY SEQUENCE

1. Load module.yaml

Read {targetPath}/module.yaml

IF not present:

Record as FAIL (required file)
Skip to next validation

2. Validate Required Fields

Check required fields (must have actual values, not placeholders):

code: present (kebab-case, 2-20 chars, starts with letter)
name: present (non-empty string)
header: present (non-empty string)
subheader: present (non-empty string)
default_selected: present (boolean)

3. Validate Custom Variables

For each custom variable:

prompt: present
default: present (or explicitly omitted)
result: template valid
Variable naming correct (kebab-case)

For single-select:

single-select: array present
All options have value: and label:

For multi-select:

multi-select: array present
All options have value: and label:

4. Validate Extension Module Code

IF Extension:

code: matches base module code
This is intentional (not an error)

5. Record Results

Append to {validationReportOutput}:

## module.yaml Validation

**Status:** {PASS/FAIL/WARNINGS}

**Required Fields:** {status}
**Custom Variables:** {count} variables
**Issues Found:**
{list any issues}

6. Auto-Proceed

"✓ module.yaml check complete."

Proceeding to next validation...

Load {nextStepFile}

Success Metrics

✅ All module.yaml checks performed ✅ Results recorded ✅ Auto-proceeds to next validation

2.2 KiB Raw Blame History