Convert decomposed epic items into formatted user story Markdown files.
npx skills add https://github.com/epieczko/betty --skill story-write
Please help me install this Agent Skill. Skill: story.write Source: https://github.com/epieczko/betty/tree/main/skills/story.write Command: npx skills add https://github.com/epieczko/betty --skill story-write
Convert decomposed items from epic.decompose into fully formatted user stories. This skill generates individual Markdown files for each story following standard user story format, enabling traceable implementation steps.
python3 skills/story/write/story_write.py
--stories_file_(string,_required):path_to_the_stories.json_file_from_epic.decompose "value"
--epic_reference(string,_optional):reference_to_the_source_epic_for_traceability "EPIC-001"
--output_dir(string,optional):directory_to_save_story_files(default:./stories/) "value" \
High-intent search queries and answers about installing and using this skill.
User story conversion takes decomposed items from epic.decompose and generates individual story_<n>.md files with persona, goal, acceptance criteria, and metadata. The Skill reads a stories.json payload, validates inputs, and creates a stories_index.md summary for traceability in your output directory.
Story.write produces Markdown files following standard user story format, each containing an ID, persona, goal statement, benefit, acceptance criteria, and optional epic reference. A stories_index.md index file summarizes all generated stories for cross-referencing.
Yes. The Skill accepts an optional epic_reference parameter to include traceability metadata in each story file, enabling you to maintain the connection between decomposed stories and their parent epic throughout implementation workflows.
Story.write requires a stories.json file produced by epic.decompose containing decomposed items. You supply the file path via the --stories_file parameter; output directory and epic reference are optional and default to ./stories/ and none respectively.
Yes. Story.write is designed for batch generation of INVEST-aligned user stories from epic decomposition. It validates inputs, writes individual story files, and generates a traceability index—ideal for teams implementing stories at scale with consistent formatting.
Story.write has dependencies on json and yaml libraries. It reads stories.json payloads from epic.decompose; YAML support in dependencies enables flexibility in preprocessing or configuration stages of your epic decomposition workflow.
LucaDeLeoDecompose natural-language project goals into epics and user stories with acceptance criteria.
FabienDehopreConvert existing conversations into structured product requirements documents.
qa-amanDecompose approved epics into sprint-ready sub-epics with story-point estimates.
xloxn69Generates a complete user story template with YAML frontmatter and markdown sections.
