propose-implementation-plan

To generate a TOML implementation plan, the Skill analyzes your design document and test plan to output a machine-readable TOML file with commit boundaries, dependencies, and acceptance criteria.

Atomic commit planning coordinates small, self-contained commits toward a complete feature, ensuring consistent, auditable progress tracking through machine-readable implementation plans.

You map acceptance criteria and tests by generating an implementation plan that ensures end-to-end traceability, linking tests from the test plan directly to their corresponding atomic commits in the TOML output.

You define commit boundaries and dependencies by creating an implementation-plan.toml file, which uses dependency-driven planning to clarify execution order and validate the TOML structure for your repository.

Yes, the Skill validates the TOML structure automatically when generating the implementation plan, ensuring the commit boundaries, dependencies, and acceptance criteria are correctly formatted and machine-readable.

You need a machine-readable implementation plan when you want to coordinate atomic commits toward a complete feature and enable consistent, auditable progress tracking across your project workflow.