create-epic

Generate structured epic JSON with vision, architecture, and unique ID.

13|1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/Roeia1/SAGA --skill create-epic-roeia1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-epic
Source: https://github.com/Roeia1/SAGA/tree/main/plugin/skills/create-epic
Command: npx skills add https://github.com/Roeia1/SAGA --skill create-epic-roeia1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams automate the creation of epic definitions by collecting a vision and architecture, validating input, and producing a structured JSON artifact for downstream workflows.

Core Features & Use Cases

  • Validate an initial epic description and guide refinement through an interactive dialog to capture overview, goals, and scope.
  • Generate a unique, URL-friendly epic ID, and check for duplicates before creating the epic JSON.
  • Engage in dialog to compose the Architecture and Vision sections, then save the final epic as .saga/epics/<id>.json with a comprehensive description.
  • Produce a concise epic title and full markdown description to support downstream story generation.

Quick Start

Run /create-epic "User authentication with OAuth" to begin drafting an epic and produce its JSON artifact.

Frequently Asked Questions about create-epic

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

FAQPage Schema
How do I automate epic creation and generate structured JSON for project management?

Automating epic creation involves validating an initial description, guiding dialog for vision and architecture, and writing structured JSON to .saga/epics/<id>.json. This process captures overview, goals, and scope while generating a unique, URL-friendly ID.

What is the best way to define an epic vision and architecture notes in a structured format?

Defining an epic vision and architecture notes uses an interactive dialog to compose these sections, producing a concise title and full markdown description. The final output saves as a JSON artifact for downstream story generation workflows.

How do I generate a URL-friendly epic ID and check for duplicates before writing project data?

Generating a URL-friendly epic ID occurs after validating the initial description and verifying non-existence of duplicates. The system checks for existing entries before creating the epic JSON file at the specified path.

Can I use an interactive dialog to refine epic scope and goals before producing a JSON artifact?

Interactive dialog guides refinement of epic scope, goals, and overview before generating the final JSON artifact. The dialog engages users to compose Architecture and Vision sections, ensuring comprehensive epic definitions.

Does epic planning automation support downstream story generation from JSON files?

Epic planning automation produces a JSON artifact with a comprehensive description, concise title, and full markdown description. This structured output specifically supports downstream story generation workflows.

Why does my epic JSON file need a YAML frontmatter with name and description?

YAML frontmatter containing name and description satisfies requirements for a Skill Unit structure. The epic JSON file stores the output at .saga/epics/<id>.json with comprehensive epic data including vision and architecture notes.