Start Yaml Config Generator

Outputs

• YAML updates (new keys, removed keys)
• Wiring updates in start module to read only the new keys
• Optional tests when wiring logic is complex (extract class + unit test)

Naming & Packaging

• Keys must follow start-config-schema-guardrails; this skill applies the change to actual YAML files and related wiring.
• Keep config groups coherent, e.g.:
  • persimmon.kafka.producer.*
  • persimmon.kafka.consumer.*
  • persimmon.outbox.relay.*

Rules

• If user says “no backward compatibility”, remove old keys and do not implement fallback reads.
• If the change affects multiple modules (adapter consumer + start yaml + wiring), update all in one patch.
• If a key is required for local Spring Boot startup in a *-start module, prefer a committed YAML default or application-local.yaml value over an external environment-file prerequisite.
• Do not move mandatory local startup configuration into dotenv or manually prepared environment files for the final runnable gate.

Reference Implementations

• YAML baseline:
  • {{startModuleDir}}/src/main/resources/application.yaml
  • {{startModuleDir}}/src/main/resources/application-local.yaml
  • {{startModuleDir}}/src/main/resources/application-example.yaml
• Guardrails:
  • <active-skill-root>/start-config-schema-guardrails/SKILL.md

Tests

• Prefer unit tests for extracted policy classes; wiring itself is typically covered by startup smoke tests.

Common Mistakes

Integration

• Called by: scaffold-router
• Pairs with: start-config-schema-guardrails, start-wiring-config-generator, adapter-mq-consumer-generator

Commit Gate

• pass required tests (mvn -q clean test minimum, mvn -q clean verify if DB behavior changed)
• run requesting-code-review
• resolve Critical/Important findings
• keep the commit focused