vertical-slice

Name: vertical-slice
Availability: InStock
Author: Lotea

Organize feature changes into end-to-end vertical slices with per-slice checkpoints and model annotations.

2|Updated Jun 6, 2026

Search Tags:#end-to-end #quality-assurance #software-design #incremental-delivery #vertical-slices #slice-planning #agile-guidance

Ready to run

npx skills add https://github.com/lotea-be/qrspi --skill vertical-slice-lotea-be

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vertical-slice
Source: https://github.com/lotea-be/qrspi/tree/main/claude/skills/vertical-slice
Command: npx skills add https://github.com/lotea-be/qrspi --skill vertical-slice-lotea-be

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose feature work into end-to-end vertical slices to enable incremental delivery, faster feedback, and clearer demos, avoiding the pitfalls of horizontal layering that hide dependencies until late in the process.

Core Features & Use Cases

End-to-end slice scaffolding: for each user-visible capability, provide a Mock API, Frontend component, and an eventual Real DB update, all under a single slice.
Checkpoints and Model annotations: each slice ends with a checkpoint and uses a Model tag (Model: sonnet|opus) to guide implementation and planning.
Guidance on anti-patterns and when to prefer horizontal layering.

Quick Start

Outline the first vertical slice and run /qrspi:implement to start implementing it.

Frequently Asked Questions about vertical-slice

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

FAQPage Schema

What are vertical slices in software design and how do they help incremental delivery?▼

Vertical slices decompose feature work into end-to-end user-visible capabilities, spanning mock APIs, frontend, and real database layers. This approach enables incremental delivery and faster feedback by avoiding horizontal layering that hides dependencies until late in the process.

How do I plan multi-stage UI and database changes using vertical slices?▼

You plan multi-stage UI and database changes by organizing each user-visible capability into a single slice containing a mock API, frontend component, real database update, and tests. Each slice ends with a checkpoint and model annotation to guide implementation.

When should I prefer horizontal layering over end-to-end vertical slices?▼

You should prefer horizontal layering over vertical slices when end-to-end feature decomposition is impractical or obscures dependency resolution. The Skill provides specific guidance on avoiding anti-patterns and identifying scenarios where horizontal layering is the better architectural choice.

How do model annotations and checkpoints work during slice planning?▼

Model annotations use a tag (Model: sonnet|opus) to guide implementation and planning for each slice. Checkpoints mark the end of a slice, ensuring all steps—mock API, frontend, real database, and tests—are completed before progressing to the next incremental delivery phase.