skills.rest
ctejada85
ctejada85COMMUNITY
Explore all skills by this author →
GitHub

basic-documents-userstory-write

Generate user story ticket files with structured story, description, acceptance criteria, and tasks.

Updated Sep 29, 2025
Search Tags:#documentation#bug fix#agile#feature#ticket#user story
One-click install
npx skills add https://github.com/ctejada85/adrakestory --skill basic-documents-userstory-write
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: basic-documents-userstory-write
Source: https://github.com/ctejada85/adrakestory/tree/main/.claude/skills/basic-documents-userstory-write
Command: npx skills add https://github.com/ctejada85/adrakestory --skill basic-documents-userstory-write

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill streamlines the process of creating well-defined user story tickets, ensuring all necessary components like story, description, acceptance criteria, and tasks are included for clear implementation.

Core Features & Use Cases

  • Structured Ticket Creation: Generates user story files with a consistent, predefined format.
  • Guided Documentation: Provides clear guidelines on what information to include for each section (story, description, AC, NFRs, tasks).
  • Use Case: When a new feature is proposed, use this Skill to quickly generate a ticket.md file that developers can use as a clear specification for implementation.

Quick Start

Use the basic-documents-userstory-write skill to write a user story for the new login feature.

Frequently Asked Questions about basic-documents-userstory-write

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

FAQPage Schema
How do I write a structured user story for a new feature?▼

To write a structured user story, this Skill generates a ticket file containing the story, description, acceptance criteria, non-functional requirements, and tasks to ensure clear feature implementation.

What is the best way to document a bug fix as a user story ticket?▼

Documenting a bug fix as a user story requires generating a structured ticket file that captures the story, description, acceptance criteria, non-functional requirements, and implementation tasks.

What should be included in an agile user story ticket?▼

An agile user story ticket should include the story description, detailed context, acceptance criteria, non-functional requirements, and a breakdown of implementation tasks.

Do I need a specific template format to create user story tickets?▼

Yes, creating user story tickets requires an assets/userstory-template.md file and a SKILL.md file to guide the structured generation of the story, acceptance criteria, and tasks.

Can I use this to generate tickets for both features and bug fixes?▼

Yes, you can generate structured user story ticket files for both new feature proposals and bug fixes to provide developers with clear implementation specifications.

Related Skills

Explore More Product & Management Skills→
jabrenajabrena
423

014-agile-user-story

Generate Agile user stories and Gherkin feature files from structured inputs.

Community
Intermediate
allaydesaiallaydesai
2

bmad-sprint-planning

Parse epic and story markdown files to generate sprint-status.yaml summaries.

Community
Intermediate
webn77webn77

user-story

Convert persona and feature inputs into user stories with acceptance criteria.

Community
Intermediate
1479089714790897
7

kwp-product-management-write-spec

Generate structured product requirement documents from unstructured problem statements.

Community
Intermediate