vertical-slice

Divide software features into small end-to-end slices for iterative development.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/FScoward/senju --skill vertical-slice-fscoward
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vertical-slice
Source: https://github.com/FScoward/senju/tree/main/skills/vertical-slice
Command: npx skills add https://github.com/FScoward/senju --skill vertical-slice-fscoward

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It simplifies incremental feature development by creating small, end-to-end functional slices, enabling faster feedback and easier maintenance.

Core Features & Use Cases

  • Incremental Development: Break down complex features into manageable slices that deliver immediate value.
  • End-to-End Functionality: Each slice includes database, backend, and frontend for full user flows.
  • Use Case: Implementing a new user registration process in small steps, each providing working functionality before adding additional features or layers.

Quick Start

Describe the task of gradually adding a new feature by creating small, independently deployable slices that progressively expand system capabilities.

Frequently Asked Questions about vertical-slice

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is vertical slicing in incremental software development?

Vertical slicing is an incremental development technique that divides complex features into small, end-to-end functional slices, enabling faster feedback and easier maintenance.

How do I break down complex features into end-to-end vertical slices?

Divide complex features by creating small, independently deployable slices where each slice includes database, backend, and frontend layers to deliver full user flows and immediate value.

When should I use vertical slices for feature decomposition?

Use vertical slices for feature decomposition when implementing complex workflows like user registration, allowing you to deliver working functionality progressively before adding additional features.

Does vertical slicing require frontend, backend, and database layers in every slice?

Yes, vertical slicing requires each slice to include database, backend, and frontend components to ensure end-to-end functionality and full user flows for early delivery and validation.

What is the best way to implement a new feature incrementally using vertical slices?

The best way to implement a feature incrementally is creating small, independently deployable slices that progressively expand system capabilities, validating each working functionality before adding more layers.

Why use vertical slices instead of building horizontal layers incrementally?

Vertical slices enable early delivery and validation by providing end-to-end functionality across all layers, whereas horizontal layering delays working user flows until all separate layers are fully integrated.