construction

To implement an approved execution plan with TDD and gated commits, the Skill coordinates development, refinement, auditing, and adversarial validation for each execution group sequentially. It enforces tests, auditing, and explicit human approval before producing one verified commit per group.

The best way to enforce code audits and adversarial validation before a git commit is using a specification-driven workflow that gates commits. This Skill requires passing audits, persisted implementation validation results, and adversarial diff review before generating an authorized commit.

To handle unchecked tasks in a specification-driven feature plan, the Skill processes each execution group sequentially. It resolves failures, validates the resulting diff, and prepares the completed work for human-approved commit, ensuring no untested or unaudited changes proceed.

Yes, explicit human approval is required for every execution group in TDD development using this approach. The workflow mandates human approval alongside passing tests, code audits, and persisted implementation validation before generating a single verified commit per group.

Yes, you can use this gated commit workflow for bug fixes and refactors, as well as specification-driven feature work. The execution groups organize all these task types through the same TDD, adversarial validation, and auditing gates before committing.

Adversarial diff review prevents untested code from being committed by acting as a validation gate within the execution group workflow. It requires persisted implementation validation results and explicit human approval before authorizing any verified commit, blocking unauthorized changes.