user-story-writer

Decompose feature requirements into INVEST-compliant user stories with acceptance criteria.

12|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jikig-ai/soleur --skill user-story-writer-jikig-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story-writer
Source: https://github.com/jikig-ai/soleur/tree/main/plugins/soleur/skills/user-story-writer
Command: npx skills add https://github.com/jikig-ai/soleur --skill user-story-writer-jikig-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts ambiguous feature requirements into thin, testable, user-focused stories that deliver measurable business value and reduce planning friction.

Core Features & Use Cases

  • Elephant Carpaccio vertical slicing to create the smallest end-to-end deliverable increments.
  • Enforcement of INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) for every story.
  • Structured story templates including acceptance criteria and definition of done, plus prioritization guidance for backlog sequencing.
  • Use cases: sprint planning, backlog refinement, decomposing vague requirements into actionable work items.

Quick Start

Decompose the feature "Allow users to share playlists" into prioritized INVEST-compliant user stories with acceptance criteria and a definition of done.

Frequently Asked Questions about user-story-writer

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

FAQPage Schema
How do I decompose vague feature requirements into actionable user stories for sprint planning?

To decompose vague feature requirements for sprint planning, apply Elephant Carpaccio vertical slicing to break features into the smallest end-to-end deliverable increments, producing INVEST-compliant, testable work items with clear acceptance criteria and definitions of done.

What is Elephant Carpaccio vertical slicing in product management?

Elephant Carpaccio vertical slicing is a product management technique that decomposes features into thin, end-to-end deliverable increments, ensuring each increment delivers measurable business value and can be independently tested.

How do I ensure my backlog refinement produces INVEST-compliant user stories?

To ensure backlog refinement produces INVEST-compliant user stories, structure each story to be Independent, Negotiable, Valuable, Estimable, Small, and Testable, while including prioritization guidance for backlog sequencing and a clear definition of done.

What is the best way to write acceptance criteria for vertically sliced user stories?

The best way to write acceptance criteria for vertically sliced user stories is to apply Elephant Carpaccio to create thin increments, then define clear testable conditions and definitions of done that verify the increment delivers the intended business value.

Can I use this approach to convert ambiguous product requirements into testable work items?

Yes, you can convert ambiguous product requirements into testable work items by applying vertical slicing and INVEST criteria enforcement to produce granular, implementable stories with prioritized sequencing for backlog refinement.

When should I not use thin vertical slicing for user story decomposition?

You should avoid thin vertical slicing for user story decomposition when features require significant architectural groundwork before delivering any measurable business value, or when the product requirements lack sufficient clarity to define end-to-end testable increments.