slice

Break a plan into end-to-end vertical slices covering schema, backend, API, UI, and tests.

71|17|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/AgentiveStack/skills --skill slice-agentivestack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slice
Source: https://github.com/AgentiveStack/skills/tree/main/slice
Command: npx skills add https://github.com/AgentiveStack/skills --skill slice-agentivestack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks a plan into thin, end-to-end vertical slices that deliver a complete path through all layers (schema, backend, API, UI, and tests).

Core Features & Use Cases

  • Draft tracer-bullet slices that cover all layers end-to-end.
  • Ensure each slice is independently demoable and verifiable.
  • Choose AFK or HITL slice types and manage dependencies between slices.

Quick Start

Identify your current feature or spec and draft the first minimal end-to-end tracer bullet that validates the core path.

Frequently Asked Questions about slice

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

FAQPage Schema
How do I break a feature plan into end-to-end vertical slices?

To break a feature plan into end-to-end vertical slices, you draft thin tracer-bullet paths that cut through schema, backend, API, UI, and tests. This ensures each slice delivers an independently demoable and verifiable feature path.

What is a tracer-bullet slice in software workflow planning?

A tracer-bullet slice in workflow planning is a minimal, end-to-end implementation path spanning all layers from schema to UI. It validates the core architecture early by delivering a complete, testable, and demoable vertical path through the system.

How do I manage dependencies between AFK and HITL slices?

You manage dependencies between AFK (Away From Keyboard) and HITL (Human In The Loop) slices by defining deterministic slice types during planning. This records blockers and expectations, ensuring traceable milestones across the implementation workflow.

Does vertical slice planning work for features defined by a spec?

Vertical slice planning works directly with features defined by a spec. It uses the spec to drive implementation by breaking it into traceable slices and milestones that cover schema, backend, API, UI, and testing scope.

What is the best way to ensure each feature slice is independently testable?

The best way to ensure each feature slice is independently testable is to define deterministic slice types and specify testing scope for each. This approach records expectations and blockers, making every vertical slice verifiable end-to-end.