spdd-story

Decompose feature requirements into INVEST-compliant development stories.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/gabbello/medicine-plan --skill spdd-story-gabbello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spdd-story
Source: https://github.com/gabbello/medicine-plan/tree/main/.agents/skills/spdd-story
Command: npx skills add https://github.com/gabbello/medicine-plan --skill spdd-story-gabbello

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps transform high-level feature requirements into structured, INVEST-compliant development stories with clear scope boundaries and testable acceptance criteria.

Core Features & Use Cases

  • INVEST Analysis: Analyze and validate the INVEST principles in the stories.
  • Story Decomposition: Break down features into independently deliverable stories.
  • Business-Focused ACs: Generate acceptance criteria using Given-When-Then format.
  • Story Sizing: Estimate effort based on story complexity and team capacity.
  • Output Documentation: Create comprehensive story documents with detailed information.

Quick Start

Decompose the feature requirement "Implement team management API with CRUD operations" into a structured story.

Frequently Asked Questions about spdd-story

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

FAQPage Schema
How do I decompose high-level feature requirements into agile development stories?

To decompose feature requirements, this Skill breaks down high-level business objectives and feature documentation into structured, independently deliverable development stories using the INVEST methodology.

What is the INVEST methodology for story decomposition?

The INVEST methodology validates that development stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. This Skill analyzes feature requirements against these principles to ensure proper story decomposition.

How do I write acceptance criteria for agile development stories?

You generate business-focused acceptance criteria for development stories using the Given-When-Then format, ensuring clear scope boundaries and testable conditions derived from your feature documentation.

Can I estimate story sizing based on feature complexity and team capacity?

Yes, you can estimate development effort by analyzing story complexity alongside your team capacity, allowing you to size stories appropriately during the agile decomposition process.

What is the best way to break down a CRUD API feature into structured stories?

The best way to break down a CRUD API feature is to analyze business objectives and decompose the functionality into independently deliverable stories with clear scope boundaries and testable acceptance criteria.

Do I need user stories and feature documentation to generate INVEST-compliant stories?

Yes, this Skill requires analysis of existing user stories, feature documentation, and business objectives as input to effectively decompose and validate high-level requirements into structured stories.