superbuild

To enforce a definition of done across phased implementation plans, you provide a superplan-formatted plan document so the system can coordinate phased execution with automated quality gates like linting, formatting, type checks, and tests before phase advancement.

Automate quality gates during plan execution by letting the system run language-specific verification steps such as lint, format, type check, and tests, ensuring iterative validation passes before updating the plan and advancing to the next phase.

Yes, you can execute parallel phases in a multi-phase implementation plan. The system supports parallel phases via sub-agents, ensuring that defined quality gates are still met and the plan is updated after each phase completes for traceability.

To generate conventional commit messages after completing a development phase, the system evaluates the completed work against the plan, updates the plan document, and outputs a conventional commit message for you to review and apply.

The best way to maintain an auditable trail of progress during plan execution is to use a system that updates the plan document after each phase, recording validation results and phase completion status to ensure strict traceability throughout the workflow.

Yes, you need a superplan-formatted plan document. The system reads this specific format to coordinate phased execution, enforce strict definition of done checks, and output conventional commit messages for user review.