large-feature-workflow

Large feature development requires a structured workflow with phase-based planning, execution, and validation. This approach generates a detailed 4-8 phase plan with dependencies, acceptance criteria, and validation commands to ensure focused implementation and progress.

Phase-based planning breaks down large features into 4-8 distinct phases, each with dependencies, acceptance criteria, and validation commands. This mechanism ensures systematic implementation by starting fresh sessions for each phase and running validators at phase boundaries.

Managing large feature implementation integrates with version control by committing per phase and creating PRs for each phase. This ensures backward compatibility and independent mergeability, allowing systematic progress without destabilizing the main branch.

Validating large features at each implementation phase involves running validators at phase boundaries and updating the plan accordingly. This ensures focused implementation sessions meet acceptance criteria before proceeding to the next development phase.

A structured phase-based workflow is ideal for large-scale feature development where a systematic approach is crucial. It ensures quality and progress by enforcing phase-based execution, boundary validation, and independent mergeability for complex software engineering tasks.

Phase-based workflows are not suitable for small or trivial changes that do not require 4-8 phases of structured planning. Overhead from boundary validation and independent phase PRs outweighs the benefits for simple feature implementations.