unify

Validate spec-group convergence across requirements, atomic specs, implementations, and tests.

Updated Mar 23, 2026

Search Tags:#convergence #spec #traceability #test-evidence #atomic-spec #implementation-evidence

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns a spec group's progress by validating that requirements, specs, atomic specs, implementations, and tests are complete and consistently aligned.

Core Features & Use Cases

End-to-end convergence checks: verify that REQ-to-atomic spec-to-implementation-to-test chains are intact and auditable.
Traceability validation: ensure all requirements map to atomic specs and all ACs map back to requirements.
Quality gating: confirm readiness before code reviews and merges in multi-workstream environments.

Quick Start

Run /unify <spec-group-id> to validate full convergence of a spec group after implementation and testing.

Frequently Asked Questions about unify

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

FAQPage Schema

How do I validate traceability between requirements, atomic specs, and tests?▼

Validate traceability by verifying that requirements map to atomic specs and all acceptance criteria map back to requirements. This convergence check ensures the REQ-to-atomic spec-to-implementation-to-test chains are complete, intact, and auditable before code reviews.

What is spec group convergence and when do I need to check it?▼

Spec group convergence is the validation that requirements, specs, atomic specs, implementations, and tests are complete and consistently aligned. You need to check it after implementation and testing to confirm comprehensive readiness for code reviews and merges.

How do I enforce quality gating for spec alignment in multi-workstream environments?▼

Enforce quality gating by validating spec group convergence to confirm readiness before merges in multi-workstream environments. This requires checking that manifest review_state is APPROVED, atomic_specs enforcement_status is passing, and work_state is VERIFYING.

Does spec convergence validation work without an approved manifest review state?▼

Spec convergence validation does not work without an approved manifest review state. It enforces that manifest.review_state is APPROVED, atomic_specs.enforcement_status is passing, and work_state is VERIFYING before allowing comprehensive traceability validation.

What is the best way to verify implementation evidence aligns with atomic specs?▼

The best way to verify implementation evidence alignment is to validate end-to-end convergence checks across the spec group directory. This ensures that every requirement traces directly through atomic specs to the implementation and test evidence without missing links.