implement-commit

To automate TDD commits from an implementation plan, this Skill parses a TOML plan and orchestrates Designer, Tester, Implementor, Arbiter, and Scope phases to execute commits in dependency order with gate and formatter checks.

A deterministic commit pipeline processes implementation plans by resolving dependencies, applying style reviews, and logging progress in a ledger to ensure consistent, automated feature commits through isolated TDD phases.

Yes, you need an implementation-plan.toml file located at docs/features/NNNN-name/ to run automated commits, as the pipeline parses this file to manage dependency resolution and orchestrate the required TDD phases.

Yes, you can run style reviews and scope checks automatically during commit execution, as the pipeline applies gate and formatter checks while orchestrating the Implementor and Arbiter phases to consolidate results.

The best way to manage dependency resolution for feature commits is using a plan-driven pipeline that parses TOML files to sequence commits based on dependencies and logs progress in a ledger.

Commit automation isolates execution into separate Designer, Tester, Implementor, Arbiter, and Scope phases to enforce deterministic TDD gates, ensuring style reviews and dependency resolution are consistently validated before logging progress.