Configuration Management

Goal

Establish a single, coherent software configuration management (SCM) discipline so that every released artifact is identifiable, reproducible, traceable to its sources, and changed only through a controlled process. This skill operationalizes the SWEBOK v4 "Software Configuration Management" knowledge area: selecting a branching strategy, identifying baselines and releases, controlling change, producing reproducible builds, identifying artifacts and versions, generating a software bill of materials (SBOM), and auditing configuration. It unifies practices that live in adjacent skills — git-workflow.skill for the mechanics of branching and commits, release-management.skill for cutting and shipping releases, and dependency-lifecycle.skill for managing third-party components — and binds them into one SCM plan.