development-workflow

A structured development workflow organizes multi-commit features into a five-phase lifecycle: DESIGN, IMPLEMENT, REFINE, DOCUMENT, and REVIEW. It coordinates cross-functional tasks like design planning, test-driven coding, and final reviews to produce tangible artifacts.

You coordinate feature design and implementation by drafting a design plan first, then proceeding with test-first development. This structured workflow enforces incremental commits and synchronizes coding, testing, and documentation across the feature lifecycle.

Manage code reviews and documentation by following a prescribed workflow that outputs updated docs and a final REVIEW.md. The process ensures documentation is updated during the DOCUMENT phase and evaluated during the REVIEW phase.

Yes, test-driven development is a core emphasis of this workflow. During the IMPLEMENT phase, you write tests first to guide coding, ensuring quality before moving to refinement, documentation, and final review.

Use a phase-based development workflow when your work spans multiple commits and involves cross-functional tasks like design, implementation, testing, and documentation. It is ideal for significant changes that require structured coordination from planning to release.

Expected outputs include a design document, incremental commits, updated documentation, and a final REVIEW.md. These output-driven artifacts ensure every phase from design to review produces tangible, verifiable results.