draft-epic

Draft GitLab Epic sections by aggregating data from GitLab, Slack, and Redmine.

Updated Dec 24, 2025

Search Tags:#documentation #product management #requirements gathering #user stories #gitlab #epic

One-click install

npx skills add https://github.com/MakotoUwaya/dotfiles --skill draft-epic

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: draft-epic
Source: https://github.com/MakotoUwaya/dotfiles/tree/main/.config/claude-code/skills/draft-epic
Command: npx skills add https://github.com/MakotoUwaya/dotfiles --skill draft-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires glab, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of GitLab Epics by interactively guiding users through filling out essential template sections, ensuring comprehensive and well-structured Epic descriptions.

Core Features & Use Cases

Interactive Section Filling: Guides users to complete sections like Goals, Background, User Stories, Hypotheses, and Functional Requirements.
Information Aggregation: Gathers data from GitLab Epics, Slack threads, Redmine tickets, and related Epics.
Clarification Prompts: Asks users for input on ambiguous technical decisions, MVP scope, and user story details.
Use Case: When tasked with creating a new Epic for a feature, use this Skill to ensure all necessary context, scope, and requirements are captured systematically, even when starting from a vague idea.

Quick Start

Use the draft-epic skill to help me write a new GitLab Epic for the user authentication feature.

Frequently Asked Questions about draft-epic

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

FAQPage Schema

How do I create a GitLab Epic with structured user stories and functional requirements?▼

To create a GitLab Epic with structured user stories and functional requirements, use this Skill to interactively draft sections like goals, background, and hypotheses. It aggregates context from GitLab and Redmine to ensure comprehensive Epic descriptions.

Can I aggregate context from Slack and Redmine when drafting GitLab Epics?▼

Yes, you can aggregate context from Slack and Redmine when drafting GitLab Epics. The Skill gathers data from Slack threads, Redmine tickets, and related GitLab Epics to prompt users for clarification on scope and technical decisions.

What is the best way to define MVP scope for a new product feature Epic?▼

The best way to define MVP scope for a new product feature Epic is using interactive clarification prompts. The Skill asks targeted questions about ambiguous technical decisions and scope boundaries, ensuring all necessary context is captured systematically.

Does this interactive Epic drafting tool require the glab CLI to update issues via API?▼

Yes, this interactive Epic drafting tool requires the glab CLI. It depends on the glab command-line tool to authenticate and update GitLab Epics via the API upon completion of the interactive drafting process.

How do I systematically fill out GitLab Epic templates from a vague idea?▼

To systematically fill out GitLab Epic templates from a vague idea, use the Skill's interactive section filling feature. It guides you through completing sections like Goals, User Stories, Hypotheses, and Functional Requirements step by step.

When should I avoid using an interactive Epic generator for requirements gathering?▼

You should avoid using an interactive Epic generator when your requirements gathering needs rapid bulk creation of standardized Epics without scope clarification. The Skill is designed for comprehensive, step-by-step interactive drafting rather than high-volume automated generation.