enforce

Validate atomic spec groups for granularity and coverage.

Updated Mar 23, 2026

Search Tags:#workflow #validation #reporting #manifest #atomicity #specs #enforce

Ready to run

npx skills add https://github.com/mattphanm/Codex-Agentic --skill enforce

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: enforce
Source: https://github.com/mattphanm/Codex-Agentic/tree/main/.codex/skills/enforce
Command: npx skills add https://github.com/mattphanm/Codex-Agentic --skill enforce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that atomic specs are appropriately granular, avoiding over- or under-splitting to ensure maintainable and testable components.

Core Features & Use Cases

Atomicity validation: checks each spec group for proper granularity and complete coverage.
Enforcement workflow: generates enforcement reports and updates manifest.json with status.
Integration-ready: works with existing manifest.json, requirements.md, and atomic/ directories to guide refinement.

Quick Start

Run /enforce to validate the active spec group in the repository.

Frequently Asked Questions about enforce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate atomic specs for proper granularity and coverage?▼

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.

What is the best way to enforce atomicity criteria in a modular design workflow?▼

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.

How does manifest.json enforcement status updating work?▼

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.

Do I need a specific directory structure to validate spec atomicity?▼

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.

Why does spec validation report over-splitting or under-splitting in modular components?▼

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.