story-splitting

Split large user stories by detecting linguistic red flags and applying heuristics.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Envy-7z/mobile-agent-skillpack --skill story-splitting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-splitting
Source: https://github.com/Envy-7z/mobile-agent-skillpack/tree/main/skills/story-splitting
Command: npx skills add https://github.com/Envy-7z/mobile-agent-skillpack --skill story-splitting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the challenge of overly large or vague user stories by identifying linguistic red flags and applying proven heuristics to split them into smaller, manageable, and more valuable increments.

Core Features & Use Cases

  • Red Flag Detection: Identifies common words and phrases ("and", "or", "manage", "including") that indicate a story is too big.
  • Heuristic Application: Suggests concrete splitting techniques like "Start with Outputs", "Narrow Customer Segment", and "Dummy to Dynamic".
  • Use Case: When faced with a story like "As an admin, I can manage users and roles, including creating, editing, deleting, and assigning permissions," this Skill will break it down into several smaller, actionable stories such as "Admin can create a new user" and "Admin can assign a role to a user."

Quick Start

Use the story-splitting skill to break down the user story "As a user, I want to manage my account settings and privacy preferences, including profile information, notification settings, email preferences, and data export, with the ability to preview changes before saving."

Frequently Asked Questions about story-splitting

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

FAQPage Schema
How do I split a large user story into smaller agile tasks?

To split large user stories, this skill identifies linguistic red flags like 'and' or 'manage' and applies proven heuristics to decompose broad requirements into small, independently deliverable increments.

What are common red flags that indicate a user story is too broad?

Common red flags for overly broad user stories include words like 'and', 'or', 'manage', and 'including', which often signal bundled requirements or multiple actions combined into a single task.

What heuristics can I use for agile task decomposition?

For agile task decomposition, you can apply heuristics like 'Start with Outputs', 'Narrow Customer Segment', and 'Dummy to Dynamic' to break down vague requirements into actionable increments.

When do I need to break down user stories in requirements gathering?

You need to break down user stories when requirements are bundled, scope is too broad, or multiple actions are combined into a single task, hindering iterative development and independent delivery.

What is the best way to decompose a vague admin user story?

The best way to decompose a vague admin user story is by detecting combined actions and applying splitting techniques to generate specific, manageable tasks like 'create a new user' or 'assign a role'.