dev-flow

Automating test-driven development workflows requires orchestrating stage detection and methodology coordination end-to-end. This skill automatically identifies project phases and triggers proven frameworks for requirement specification, architecture design, TDD coding, and quality gating without manual selection.

Integrating methodologies like OpenSpec, BMAD, and AI-DLC into a single workflow eliminates manual framework switching. This skill combines multiple proven development frameworks into a seamless automated pipeline, coordinating each methodology at its appropriate stage automatically.

Yes, you can skip non-critical stages and focus on coding implementation. While the skill automatically detects project phases and triggers corresponding methodologies, it allows flexible user overrides to jump between stages or isolate specific phases like test-driven coding when needed.

Automated stage detection works by identifying the current project phase across six stages: requirement exploration, architecture design, coding implementation, quality verification, deployment, and retrospective. It then triggers the corresponding proven methodology to orchestrate the full development lifecycle.

No manual configuration is needed for quality gating and deployment planning in new product development. You can simply state your project goal, and the skill automatically runs through requirement clarification, architecture design, TDD-based coding, quality checks, and deployment planning end-to-end.

You should not use automated dev workflow orchestration when you need granular manual control over individual methodology selection or when working outside end-to-end software development scenarios like new product development, feature implementation, and production deployment.