create-epics-and-stories

Name: create-epics-and-stories
Availability: InStock
Author: WritzProtocol

Create epics and user stories from product requirements and architecture decisions.

3|Updated Jun 23, 2026

Search Tags:#software development #product management #epic creation #requirements decomposition #user story creation

Ready to run

npx skills add https://github.com/WritzProtocol/writz --skill create-epics-and-stories-writzprotocol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-epics-and-stories
Source: https://github.com/WritzProtocol/writz/tree/main/.agents/skills/create-epics-and-stories
Command: npx skills add https://github.com/WritzProtocol/writz --skill create-epics-and-stories-writzprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of creating epics and user stories from product requirements and architecture decisions, streamlining the software development workflow.

Core Features & Use Cases

Automated Epic Creation: Automatically generates epic titles and goals based on extracted requirements.
User Story Creation: Generates user stories with acceptance criteria directly from the requirements.
Template-based Documentation: Outputs the final documentation in a structured format, ready for development.

Quick Start

Run the skill with the 'create-epics-and-stories' command to begin the epic and story creation process.

Frequently Asked Questions about create-epics-and-stories

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

FAQPage Schema

How do I automate epic and user story creation from product requirements?▼

You can generate user stories with acceptance criteria by providing product requirements and architecture decisions as input. The Skill processes these inputs to output structured Markdown documentation containing the generated stories and epics.

What format does the epic creation output use for documentation?▼

The epic creation output uses Markdown for documentation and YAML for configuration. This template-based approach ensures the final software development specifications are structured consistently and ready for immediate use by engineering teams.

Do I need a defined project context to generate user stories and epics?▼

Yes, you need a defined project context to generate user stories and epics successfully. The Skill requires this established environment to accurately extract requirements and architecture decisions for decomposing them into actionable software development tasks.

How are architecture decisions used in requirements decomposition for software development?▼

Architecture decisions are used in requirements decomposition by serving as foundational inputs alongside product requirements. The Skill processes these decisions to automatically generate aligned epic goals and specific user stories for the software development workflow.

What's the best way to structure epics and stories for technical specification writing?▼

The best way to structure epics and stories for technical specification writing is using template-based documentation. This Skill automates the generation of epic titles and user stories with acceptance criteria, outputting structured Markdown formatted for product management workflows.