slice

Decomposes complex software features into vertical, independently shippable slices using Socratic questioning and job stories.

17|1|Updated Mar 13, 2026

Search Tags:#tdd #scoping #agile #product-development #feature-development #job-stories

Ready to run

npx skills add https://github.com/thoughtbot/rails-consultant --skill slice-thoughtbot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slice
Source: https://github.com/thoughtbot/rails-consultant/tree/main/skills/slice
Command: npx skills add https://github.com/thoughtbot/rails-consultant --skill slice-thoughtbot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the common problem of feature bloat and delivery delays by helping you decompose large, complex features into small, independently shippable, and high-value vertical slices.

Core Features & Use Cases

Socratic Scoping: Guides you through a structured conversation to define user-centric job stories rather than technical tasks.
Vertical Slicing: Ensures you cut through the entire stack—from database to UI—so every piece of work delivers tangible value.
Risk Management: Helps identify technical and user-experience risks early by sequencing slices based on value and learning.

Quick Start

Invoke the slice skill to help me break down the feature for adding a new user notification system into small, independent slices.

Frequently Asked Questions about slice

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

FAQPage Schema

How do I break down a large feature into shippable increments?▼

To break down a large feature, you can use Socratic questioning and job story frameworks to decompose complex epics into small, independently shippable vertical slices that deliver immediate user value.

What is vertical slicing in agile product development?▼

Vertical slicing in agile product development is cutting through the entire stack—from database to UI—so every piece of work delivers tangible user value and can be shipped independently.

How do I write job stories instead of technical tasks for feature development?▼

You can write job stories through a structured Socratic scoping conversation that guides you to define user-centric narratives rather than focusing on granular technical implementation tasks.

When do I need to slice features for end-to-end delivery?▼

You need to slice features when large epics cause delivery delays or feature bloat, requiring decomposition into manageable increments that include all necessary database, logic, and UI components.

Does vertical slicing help with technical risk management?▼

Yes, vertical slicing helps with risk management by identifying technical and user-experience risks early through sequencing slices based on their value and learning potential.

Best way to sequence feature slices for high-value delivery?▼

The best way to sequence feature slices is by prioritizing them based on user value and learning potential, ensuring that high-value increments are delivered first while managing risks.