sdlc-config-management

You can prevent configuration drift by managing per-product overrides to global SDLC defaults. This skill enforces strict adherence to tech-stack parameters, ensuring agents consistently apply only the deviations from factory defaults across all generated artifacts.

Two-tier precedence lookup enforces a strict rule where agents check product-specific JSON files first before falling back to global factory defaults. This mechanism ensures consistent application of tech-stack and methodology parameters across all artifacts.

You need per-product configuration overrides when a product requires deviations from global SDLC defaults, such as using MongoDB instead of default PostgreSQL. This maintains consistency by recording only the minimal necessary configuration changes.

Yes, JSON schema validation is required to maintain consistency and prevent unauthorized configuration drift. Validating product-specific overrides against defined schemas ensures that all configuration data strictly adheres to established tech-stack standards.

The best way to manage tech-stack overrides is maintaining an override-only configuration file that records deviations from factory defaults. This approach prevents redundant data and drift while ensuring agents apply specific parameters like database choices consistently.