slicing-stories

Slice Feature Briefs into ordered vertical story slices with JSON output.

2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/chriswch/praxis --skill slicing-stories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slicing-stories
Source: https://github.com/chriswch/praxis/tree/main/skills/slicing-stories
Command: npx skills add https://github.com/chriswch/praxis --skill slicing-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps product teams transform large Feature Briefs into actionable, reviewable slices by producing an ordered slice map of end-to-end story slices. It ensures slices are vertically aligned with real user value and defers acceptance criteria to downstream clarifications.

Core Features & Use Cases

  • Vertical slicing: end-to-end story slices that map to build order.
  • Walking skeletons: start with the thinnest end-to-end path that delivers value to a real user with one real integration.
  • Outputs: a canonical JSON slice-map and a human-readable Slice Map for review and approval.

Quick Start

Process the Feature Brief at .praxis/brief.md to generate a slice map and a JSON artifact for downstream clarification.

Frequently Asked Questions about slicing-stories

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

FAQPage Schema
How do I slice a feature brief into vertical story slices?

Vertical story slicing divides a feature brief into end-to-end story slices that each deliver real user value. This Skill generates an ordered Slice Map and a canonical JSON file, starting with the thinnest walking skeleton path.

What is a walking skeleton in story slicing workflows?

A walking skeleton is the thinnest end-to-end path that delivers value to a real user with one real integration. It establishes the foundational first slice in the build order before broader functionality is layered on.

How do I generate a JSON slice map from a feature brief?

You generate a JSON slice map by processing the Feature Brief at .praxis/brief.md. The Skill validates slice boundaries against the spec, enforces INVEST criteria, and writes the canonical output to .praxis/slice-map.json.

Does story slicing with this approach enforce INVEST criteria?

Yes, story slicing enforces INVEST criteria by validating each slice boundary against the Slice Map spec during generation. This ensures every vertical slice remains independent, negotiable, valuable, estimable, small, and testable.

Can I use story slicing for downstream acceptance criteria clarification?

Story slicing defers acceptance criteria to downstream clarifications rather than embedding them in the slice map. The output provides ordered build scope, allowing subsequent processes to handle detailed acceptance criteria.