epic

Create and organize project epics with markdown files for progress tracking.

55|4|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/skilluse/skilluse --skill epic-skilluse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic
Source: https://github.com/skilluse/skilluse/tree/main/.claude/skills/epic
Command: npx skills add https://github.com/skilluse/skilluse --skill epic-skilluse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured way to create and manage "Epics," which are collections of related issues for major feature areas, helping to organize large projects and track progress effectively.

Core Features & Use Cases

  • Epic Creation: Generates a standardized directory structure and markdown files (epic.md, progress.md) for new epics.
  • Issue Tracking: Allows linking and updating the status of related issues within epic.md.
  • Progress Logging: Provides a dedicated file (progress.md) for tracking sprint progress and session notes.
  • Reference Management: Facilitates the organization of design documents, specs, and other references within a dedicated directory.
  • Use Case: When starting a new major feature like a user authentication system, create an epic to group all related tasks, design documents, and track progress across sprints.

Quick Start

Use the epic skill to create a new epic named 'user-authentication'.

Frequently Asked Questions about epic

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

FAQPage Schema
How do I organize work into themes and epics for major feature areas?

To organize work into epics, you can structure related issues for major features into themes using standardized markdown files. This establishes a clear hierarchy for tracking large project initiatives.

What is the best way to track sprint progress and session notes for a feature initiative?

Tracking sprint progress is handled through a dedicated markdown file that logs session notes and milestones. This provides a historical record of feature development alongside the main epic organization.

Can I link design documents and specs to an epic for reference management?

You can attach reference documents, specs, and design files within a dedicated directory associated with the epic. This centralizes all necessary context for team alignment on the initiative.

How do I create a new epic to group related tasks for a user authentication system?

Creating a new epic generates a standardized directory structure with specific markdown files for epic details and progress tracking. This immediately groups related tasks and references for the new feature.

Does epic tracking work without external project management dependencies?

The epic tracking system operates independently using local markdown files for issue tracking and progress logging. It requires no external dependencies to manage and organize project initiatives.

When do I need to group related issues into an epic rather than tracking them individually?

You need to group related issues into an epic when managing large project features that span multiple sprints. This approach prevents fragmented tracking and ensures team alignment across complex initiatives.