dev-pabcd

To prevent rushed coding, a structured development workflow enforces sequential progression through Plan, Audit, Build, Check, and Done phases. This requires explicit user approval at critical junctures before any code generation begins.

A phased development workflow with mandatory user checkpoints orchestrates tasks through five stages: Plan, Audit, Build, Check, and Done. It halts execution at critical junctures, requiring explicit user approval to ensure alignment and prevent unverified deliverables.

To verify code quality before finalizing a task, the workflow utilizes worker processes during the Check phase to audit plans and verify code. This prevents delivering unverified work by enforcing a structured review before completion.

This structured workflow requires no external dependencies to run. It operates independently using built-in scripts and references to orchestrate the five-phase development process and manage worker processes for verification.

To start the planning phase, initiate the workflow by running the orchestration command for the Plan phase. This sets the process in motion, preparing the design and requirements before proceeding to the Audit phase.

You should not use a sequential phased development process when tasks require rapid prototyping without design audits or user approvals. The mandatory checkpoints and strict progression are designed for tasks demanding thorough verification and alignment.