user-histories-local

Generate structured user histories from requirements into markdown backlog files.

1|Updated Apr 17, 2026

Search Tags:#automation #planning #markdown #requirements #backlog #docs #user-histories

Ready to run

npx skills add https://github.com/esneiderbravo/hackaton --skill user-histories-local

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-histories-local
Source: https://github.com/esneiderbravo/hackaton/tree/main/.claude/skills/user-histories-local
Command: npx skills add https://github.com/esneiderbravo/hackaton --skill user-histories-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate clear, actionable user histories from requirements and persist them as markdown artifacts to support backlog creation, planning, and traceability.

Core Features & Use Cases

Automatically transform input requirements into structured user stories with roles, goals, and acceptance criteria.
Save histories under docs/user-histories/backlog/ and maintain an index for quick discovery.
Support multi-level granularity (epic, feature, task) and language localization.

Quick Start

Provide the initial requirements and run the tool to produce user histories saved under the backlog folder.

Frequently Asked Questions about user-histories-local

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

FAQPage Schema

How do I generate user stories from requirements automatically?▼

Generating user stories from requirements is automated by transforming input text into structured histories with roles, goals, and acceptance criteria, saving them directly as markdown planning artifacts.

Can I organize backlog creation using local markdown files?▼

Organizing backlog creation with local markdown files is supported by outputting structured histories under docs/user-histories/backlog/ and maintaining an index file for quick discovery.

Does the user story generation support multi-level granularity like epics and tasks?▼

Multi-level granularity for user stories is supported, allowing you to break down requirements across epic, feature, and task levels within your local markdown planning artifacts.

How do I maintain an index for user stories saved in a backlog folder?▼

Maintaining an index for user stories saved in a backlog folder is handled automatically by updating the backlog index using predefined templates whenever new histories are generated.

Can I localize the language for generated user histories?▼

Localizing the language for generated user histories is supported, enabling product teams to produce requirement breakdowns and markdown planning artifacts in their preferred language.

What is the best way to structure requirements into actionable backlog items?▼

Structuring requirements into actionable backlog items is achieved by transforming input requirements into user histories with defined roles, goals, and acceptance criteria, then persisting them as traceable markdown files.