aegis-module-builder

To enforce a TDD workflow, you apply Plan, Test (red), Implement (green), Verify, Polish, and Commit phases across DB migrations, API routes, services, and UI components to catch regressions early and maintain commit discipline.

The best way to bootstrap a feature in an AEGIS repository is to initiate a module-build and sequentially execute the Plan, Test, Implement, Verify, Polish, and Commit phases to ensure consistent quality gates.

Yes, the TDD feature development workflow requires aegis-quality-gates to ensure gates 1-4 remain green, verifying that DB migrations, API routes, services, and UI components pass necessary CI checks.

Running CI-CD pipelines without the full TDD cycle bypasses the Plan/Test/Implement/Verify/Polish/Commit phases, meaning you lose enforced regression checks and structured commit discipline across DB, API, and UI pipelines.

You need to use the Plan and Test phases before implementing services to establish test-driven red states, ensuring your API routes and service layers meet required quality gates before moving to the Verify and Polish stages.

The AEGIS module builder enforces specific phases for DB migrations and UI components to orchestrate a repeatable end-to-end feature pipeline, ensuring early regression detection and consistent quality gates from planning to commit.