enforce

Atomic specs validation checks each spec group for proper granularity and complete coverage. It ensures components are appropriately split to maintain testability and avoid over-splitting, requiring a manifest.json, requirements.md, and an atomic/ directory.

Enforcing atomicity criteria involves running an automated validation process that generates enforcement reports. It evaluates spec groups against atomicity rules and updates the group's manifest.json with the current enforcement status.

Manifest.json updating works by automatically writing validation results back into the group's manifest file. After checking the atomic/ directory and requirements.md for atomicity criteria, the enforcement process modifies the manifest to reflect the current validation status.

Yes, validating spec atomicity requires a specific spec group structure. Your repository must contain a manifest.json file, a requirements.md file, and an atomic/ directory for the validation workflow to properly check granularity and update enforcement status.

Spec validation reports over-splitting or under-splitting to solve the problem of inappropriate granularity in modular design. By identifying these issues in atomic specs, it ensures components remain maintainable and properly testable before updating the manifest.