Vertical Slice.instructions

# Vertical Slice Instructions

## Overview

A **vertical slice** is a small, self-contained, end-to-end implementation that cuts through all layers of the application stack, delivering a complete feature with high fidelity and a working user experience. Unlike horizontal development (which builds infrastructure first), vertical slicing delivers immediate value while testing the entire system integration.

### Key Characteristics

- ✅ **End-to-end** - Touches all layers: database, API, business logic, UI
- ✅ **Self-contained** - Can be developed, tested, and deployed independently
- ✅ **Production-ready** - Not a prototype; includes validation, error handling, styling
- ✅ **Value-focused** - Delivers working functionality users can interact with
- ✅ **Risk-revealing** - Exposes integration issues, bottlenecks, and missing patterns early
- ✅ **Estimation-enabling** - Provides data for estimating remaining work

This concept originated in the video game industry but is now widely applied in modern web development, particularly in agile methodologies and incremental delivery approaches.

## Why Use Vertical Slices?

### Benefits

**For Development:**

- Proves the full stack works together immediately
- Identifies architectural gaps and missing patterns early
- Establishes repeatable patterns for future features
- Reduces integration risk by testing connections continuously
- Enables parallel development once patterns are proven

**For Stakeholders:**

- Provides working demonstrations early and often
- Shows progress in tangible, testable functionality
- Allows for early feedback on UX and business logic
- Reduces "big bang" integration risk at the end

**For Estimation:**

- First slice reveals actual velocity vs. assumptions
- Exposes hidden complexity in tools, frameworks, or integrations
- Provides baseline for estimating remaining similar features
- Helps identify which layers need more time or expertise

### When to Use Vertical Slices

✅ **Start of a new project** - First feature proves the entire stack works
✅ **Adding major features** - Complete implementation from UI to database
✅ **Exploring new technology** - Tests integration across all layers
✅ **Proving architecture** - Validates patterns before scaling
✅ **Complex features** - Breaks down big features into deliverable increments

## Vertical Slice vs Horizontal Development

### ❌ Horizontal Development (Anti-Pattern)