plan-stories

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

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

Core Features & Use Cases

  • Vertical Slicing: Ensures stories deliver end-to-end user value.
  • INVEST Validation: Automatically checks stories against Independent, Negotiable, Valuable, Estimable, Small, and Testable criteria.
  • Idempotent Creation: Prevents duplicate story creation by detecting existing issues.
  • Use Case: A product manager can use this skill to quickly decompose a high-level feature epic into a set of well-defined user stories ready for sprint planning.

Quick Start

Use the plan stories skill to break down the epic with ID 'PROJ-123'.

Frequently Asked Questions about plan-stories

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

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

Break epics into user stories by applying vertical slicing to ensure end-to-end user value and validating each against INVEST criteria. This approach guarantees your backlog contains manageable, testable items ready for sprint planning.

What is vertical slicing in agile story breakdown?

Vertical slicing is a story breakdown technique that splits epics into stories delivering end-to-end user value rather than isolated technical components. It creates stories spanning the full stack for meaningful sprint deliverables.

How do I validate user stories against the INVEST criteria?

Validating user stories against INVEST criteria checks that each issue is Independent, Negotiable, Valuable, Estimable, Small, and Testable. This validation runs before story creation to ensure backlog quality and sprint readiness.

Can I automatically create missing user stories without duplicating existing ones?

Yes, idempotent story creation detects existing issues in your backlog and generates only the missing user stories. This prevents duplicate tickets and ensures efficient backlog management during epic decomposition.

How do I handle epic selection based on priority and dependencies?

Epic selection based on priority and dependencies identifies which epics to decompose first by evaluating relative importance and blocking relationships. This ordering ensures stories are created in the correct sequence.

Does the user story breakdown integrate with PM tools for issue creation?

Yes, the breakdown integrates with PM tools by composing with the `/write-issue` command for direct issue creation. This connects validated user stories directly to your project management workflow.