Superpower

An agentic workflow for test-driven development orchestrates phases like brainstorming, planning, and execution through specialized modules. It enforces TDD by blocking implementation unless failing tests exist, ensuring disciplined coding and verification before review.

You enforce TDD by using automation scripts that block implementation unless a failing test exists. This hard enforcement ensures code is only written to satisfy tests, maintaining strict test-driven development discipline throughout the implementation process.

You isolate feature development by creating a separate git worktree workspace. This avoids polluting your main branch, providing a clean environment for planning and executing changes before merging reviewed code back.

The best way to structure implementation planning and code review is through a phased workflow: Brainstorm, Plan, Execute with TDD, and Review. This approach routes tasks to specialized modules, ensuring spec-compliance and code-quality checks before completion.

Yes, you can use this agentic workflow for both feature work and bug fixes. It handles tasks requiring requirements clarification, safe workspace isolation via git worktrees, and strict verification before implementation through enforced TDD.

Skipping review checkpoints in test-driven development removes required spec-compliance and code-quality checks. Without these mandatory review phases, the workflow cannot validate that the implementation meets the original requirements before completion.