full-pipeline

You can automate the full architecture redesign pipeline by running a single command that triggers end-to-end orchestration across all phases, from system investigation to code generation, producing structured outputs for reviews and deployment.

Yes, you can configure the project refactoring scope by using selective phases and domain filters. This allows you to target specific parts of large legacy projects while maintaining consistent, reproducible workflows across multiple teams.

The standardized output directory structure for reproducible pipeline runs organizes generated artifacts into reports, generated, and work directories, ensuring consistent downstream adoption for infrastructure plans and code.

Yes, the pipeline orchestration is specifically designed for large legacy projects requiring consistent, reproducible workflows across multiple domains and teams, applying phase sequencing and optional skip controls for repeatable runs.

The best way to orchestrate end-to-end discovery and code generation is to execute a single command targeting your project path, which automatically handles evaluation, design, and output generation for the entire lifecycle.

You should avoid using a single-command full pipeline when you need manual control over individual discovery or design phases, as it automates end-to-end orchestration and applies standardized phase sequencing across the entire workflow.