sdlc

Automate TDD workflows by using an orchestration skill to coordinate test-driven development, run linting and type checks, and identify modified files. This end-to-end software development lifecycle workflow processes feature specs to drive validated changes with guardrails.

Prepare git commit commands by identifying modified files related to the feature spec and generating executable commit instructions. The workflow explicitly avoids automatic commits or pushes, outputting prepared commands for manual execution to maintain developer control.

The best way to orchestrate test-runner checks and TDD is using a coordinated software development lifecycle skill. It guides the workflow from spec to validated changes by running TDD first, then executing linting, type checks, and tests via the test-runner.

Yes, you can use an automated SDLC workflow with guardrails that explicitly avoid automatic commits or pushes. The workflow prepares git commit commands and identifies modified files, outputting prepared commands for manual execution to ensure developer oversight.

Yes, the automated software development lifecycle workflow is designed for feature-spec driven requests. It applies TDD orchestration and test-runner checks to the provided spec, guiding the workflow from initial spec to validated changes and identified modified files.

The SDLC workflow outputs prepared commands to enforce guardrails that avoid automatic commits or pushes. This design eliminates fragmented manual steps during TDD and test-runner execution while ensuring developers retain control over the final git commit action.