Vertical Slicing TDD Patterns FAQs

Question 1

What is the difference between Foundation and Feature cycles?

Accepted Answer

Foundation cycles establish core infrastructure like data models or authentication that all features need, while Feature cycles deliver specific user value and can often be worked on in parallel once foundations are set.

Question 2

Why should I use vertical slices instead of horizontal layers?

Accepted Answer

Vertical slices provide earlier feedback, make progress more observable to stakeholders, and reduce the risk of integration issues that often occur when horizontal layers are merged late in the process.

Question 3

Can I use this for brownfield (existing) projects?

Accepted Answer

Yes, the skill includes specific markers like [EXTEND] and [MODIFY] to handle tasks involving existing files and legacy codebases while maintaining TDD discipline.

Question 4

How does this skill implement TDD?

Accepted Answer

It structures every implementation cycle into a four-step sequence: writing a failing test (Red), implementing the minimal code to pass (Green), refactoring for quality, and demonstrating the final behavior.

Question 5

What is vertical slicing in software development?

Accepted Answer

Vertical slicing is a technique where you build a small part of every layer (UI, logic, database) for a specific feature simultaneously, rather than building entire horizontal layers (like all database tables) at once.

Vertical Slicing TDD Patterns

Vertical Slicing TDD Patterns

Key Features

Use Cases

Key Features

Use Cases