implement

You can automate phased development by loading a DEVELOPMENT_PLAN.md file, resolving the next pending phase, and executing its steps. The system applies architecture rules, runs validation gates, and updates the plan with progress, notes, and decisions for successful completion and auditing.

A development plan gate check enforces repository quality standards like lint and tests before a phase completes. You need gate checks when automating phased development to validate architecture rules and ensure gate outcomes are recorded for successful completion and auditing.

Tracking phase status involves updating the plan with progress, notes, and decisions after executing steps and applying gates. This ensures phase status and gate outcomes are recorded for auditing and resolves the next pending phase for execution.

Yes, automated plan management integrates with repository quality checks by running lint and tests as part of validation gates. This ensures architecture rules are applied and gate outcomes are recorded before updating the plan with phase completion status.

The best way to resolve the next pending phase is to load the DEVELOPMENT_PLAN.md file and let the automation identify and prepare the pending phase for execution. This ensures correct phase resolution while applying architecture rules and validation gates.