deep-work-workflow

To enforce a TDD workflow for multi-file refactoring, this Skill orchestrates a structured phase sequence from Brainstorm to Test, blocking file writes until a plan is approved and enforcing strict RED to GREEN state transitions for every code slice.

An evidence-driven development workflow requires verified receipts and passing sensors before advancing phases. You need it for complex multi-file engineering tasks to prevent architectural drift, duplicate implementations, and unverified code changes.

You can prevent premature coding across modules by applying hard phase gates that block file writes until the Research and Plan phases are complete, ensuring structured brainstorming and plan approval occur first.

Yes, you can use git worktrees to isolate feature development. This Skill supports git worktree forks and session state files to manage isolated contexts alongside phase review gates and cross-model reviews.

The best way to verify code quality in large tasks is to run mutation testing, linters, and typechecks while collecting receipts for every implemented slice, ensuring no unverified changes advance past the Test phase.

You should not use a strict phase-gated TDD workflow for simple, single-file edits or rapid prototyping where the overhead of brainstorm, research, plan, and test phases outweighs the need for strict architectural verification.