user-story

Convert feature descriptions into user stories with acceptance criteria and effort estimates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/4asaanAI/Claude-patches --skill user-story-4asaanai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story
Source: https://github.com/4asaanAI/Claude-patches/tree/main/framework-foundry/Claude%20Plugins/layaa-ai/skills/user-story
Command: npx skills add https://github.com/4asaanAI/Claude-patches --skill user-story-4asaanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts informal feature ideas, requests, or requirements into a clear, standardized user story with acceptance criteria, technical notes, and an effort estimate to reduce ambiguity and speed handoff between product and engineering.

Core Features & Use Cases

  • Structured User Stories: Produces canonical "As a [user], I want [goal], so that [benefit]" narratives suitable for backlog items.
  • Acceptance Criteria & Technical Notes: Generates clear acceptance criteria and implementation notes to guide developers and reviewers.
  • Estimation & Prioritization: Provides relative or time-based estimates to support sprint planning and prioritization.
  • Use Case: Convert a meeting note or feature request into a ready-to-implement ticket with acceptance criteria, technical considerations, and an estimate.

Quick Start

Create a user story for a feature that allows users to reset passwords, including acceptance criteria, technical notes, and a rough point estimate.

Frequently Asked Questions about user-story

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

FAQPage Schema
How do I convert feature requests into structured user stories with acceptance criteria?▼

To convert feature requests into user stories, input your informal feature description to generate canonical 'As a [user]' narratives complete with acceptance criteria, technical notes, and effort estimates for sprint-ready backlog items.

Can I generate effort estimates and technical notes from meeting notes?▼

Yes, you can generate effort estimates and technical notes directly from meeting notes by processing the text to produce sprint-ready tickets that include implementation considerations and measurable estimation formats for planning.

What is the best way to write sprint-ready backlog items from informal requirements?▼

The best way to write sprint-ready backlog items from informal requirements is to apply a standardized conversion process that extracts the goal and benefit to produce structured narratives alongside clear acceptance criteria and relative time estimates.

Does this approach support both product management and engineering workflows?▼

Yes, this approach supports both product management and engineering workflows by reducing ambiguity and speeding up handoff, converting raw requirements into a standardized format with implementation notes suitable for developers and reviewers.

How do I format user stories for sprint planning and prioritization?▼

Format user stories for sprint planning by using the 'As a [user], I want [goal], so that [benefit]' structure, ensuring each story includes clear acceptance criteria and a measurable estimation format to support prioritization.