dev-builder

Automate project setup and feature implementation by defining your tech stack, phases, and tasks in DEV-PLAN.md. The workflow then automatically scaffolds the project structure, executes features by phase, and manages dependencies using TDD and two-tier reviews.

Yes, you need a Product-Spec.md file to start the development automation workflow. The Skill requires both Product-Spec.md and DEV-PLAN.md files to read your project specifications and phase definitions before it can automatically set up the infrastructure.

Test-driven development integrates into feature implementation by executing tasks with a TDD approach and a two-tier review process for each phase. This ensures structured feature delivery and code quality validation automatically as the workflow progresses through your DEV-PLAN.md definitions.

The best way to manage dependencies during project setup is to let the workflow automatically check for required dependencies and handle installations. It reads your tech stack requirements from the project definitions and manages the installation without manual intervention.

This development workflow is designed for new projects to quickly set up infrastructure and implement features in a structured manner. It requires Product-Spec.md and DEV-PLAN.md files to define project and phase boundaries, making it best suited for starting fresh project setups.

The dev-builder workflow requires two-tier reviews for each task to enforce test-driven development standards and ensure feature implementation quality. This automated validation step checks phase execution against the DEV-PLAN.md definitions before moving forward.