pair-process-plan-stories

Break down epics into user stories using vertical slicing and INVEST validation.

6|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/foomakers/pair --skill pair-process-plan-stories
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pair-process-plan-stories
Source: https://github.com/foomakers/pair/tree/main/.claude/skills/pair-process-plan-stories
Command: npx skills add https://github.com/foomakers/pair --skill pair-process-plan-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of breaking down large epics into well-defined, manageable user stories, ensuring alignment with development best practices.

Core Features & Use Cases

  • Automated Story Generation: Transforms epics into user stories using vertical slicing and INVEST validation.
  • Idempotent Operation: Detects and skips already created stories, preventing duplicates.
  • Use Case: A Product Manager can use this skill to quickly generate a backlog of user stories from a new epic, ready for sprint planning.

Quick Start

Use the pair-process-plan-stories skill to break down the epic identified as #42.

Frequently Asked Questions about pair-process-plan-stories

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

FAQPage Schema
How do I break down epics into actionable user stories for sprint planning?

To break down epics into actionable user stories, this Skill applies vertical slicing and INVEST validation to ensure each story is manageable, independent, and ready for development.

What is vertical slicing when generating user stories from an epic?

Vertical slicing is a technique used to split epics into user stories that deliver end-to-end functionality, ensuring each story provides independent value rather than focusing on horizontal architectural layers.

How does INVEST validation work for agile user stories?

INVEST validation checks that generated user stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable, ensuring they meet agile development best practices before entering the backlog.

Can I automate user story creation without generating duplicate backlog items?

Yes, the user story generation process is idempotent, meaning it detects already created stories and skips them, preventing duplicate backlog items when run multiple times on the same epic.

Does this epic breakdown process write user stories directly to a project management tool?

Yes, the epic breakdown process composes with a capability to write the generated user stories directly to a project management tool, automating the full backlog creation workflow.

What's the best way to prepare an epic for automated user story generation?

To prepare an epic for automated user story generation, ensure it has a clear identifier and scope definition, allowing the vertical slicing and INVEST validation logic to accurately decompose it into actionable stories.