slicing-stories

Transform feature requirements into structured stories with acceptance criteria and handoffs.

Updated Apr 11, 2026

Search Tags:#planning #requirements #story #agile #handoff #feature #slicing

Ready to run

npx skills add https://github.com/jetteim/platform-workstation-bootstrap --skill slicing-stories-jetteim

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slicing-stories
Source: https://github.com/jetteim/platform-workstation-bootstrap/tree/main/agents/skills/codex-curated/slicing-stories
Command: npx skills add https://github.com/jetteim/platform-workstation-bootstrap --skill slicing-stories-jetteim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when a feature or implementation-ready slice needs to become a human-sized story packet, acceptance tests, enabler work, spec handoff, implementation-plan input, and execution context without overwhelming the user.

Core Features & Use Cases

Story budget management (7-10 stories per packet) to keep scope focused.
Types: user stories, enabler stories, spikes, hardening stories, and gating decisions for planning.
Process and format: standardized story format, implementation handoff, and gating before planning to ensure clarity and alignment.

Quick Start

Draft a complete Story packet for a feature by following the Story Format and include the Implementation Packet outline before planning.

Frequently Asked Questions about slicing-stories

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

FAQPage Schema

How do I break down feature requirements into structured agile stories?▼

To break down feature requirements into structured agile stories, transform your requirements into decomposed user, enabler, spike, and hardening stories. This approach ensures each feature slice includes clear acceptance criteria and test hooks for focused execution.

What is the best way to manage story scope for complex feature delivery?▼

The best way to manage story scope for complex feature delivery is to apply a story budget of 7-10 stories per packet. This technique keeps your agile planning focused and prevents overwhelming the development team with unmanageable implementation slices.

How do I create an implementation handoff packet for agile planning?▼

To create an implementation handoff packet for agile planning, draft a complete story packet following a standardized story format. Include an implementation packet outline with parent feature linkage, dependencies, and architecture touchpoints before gating begins.

When do I need gating decisions for feature story slicing?▼

You need gating decisions for feature story slicing when planning execution for complex requirements. Gating ensures clarity and alignment before development starts, verifying that implementation packets, dependencies, and architecture touchpoints are fully defined.

Does this story slicing approach work for spike and hardening stories?▼

Yes, this story slicing approach works for spike and hardening stories. It transforms requirements into multiple story types, including user stories, enabler stories, spikes, and hardening stories, each with structured acceptance criteria and test hooks.

Why use a standardized story format for agile requirements decomposition?▼

Use a standardized story format for agile requirements decomposition to ensure clarity and alignment during handoff. Standardizing the story packet structure coordinates feature delivery by linking dependencies and architecture touchpoints directly to execution context.