Epic - Epic Manager

Create and manage Epics for organizing related issues.

Directory Structure

project/
└── specs/
    ├── epics/
    │   ├── cli/
    │   │   ├── epic.md                   # Epic overview and issue references
    │   │   ├── progress.md               # Sprint progress tracking
    │   │   └── references/               # Reference documents
    │   │       └── Design.md
    │   └── website/
    │       ├── epic.md
    │       ├── progress.md
    │       └── references/
    └── issues/
        └── ...

What is an Epic?

An Epic is a collection of related issues grouped by major feature area or project.

Components:

• epic.md - Overview, goals, and issue references
• progress.md - Sprint progress tracking log
• references/ - Design docs, specs, requirements

When to Use

• User says "create epic", "new epic", "start project"
• Starting a new major feature area
• Organizing related issues under a theme
• Adding reference documents to an epic

Creating an Epic

Step 1: Create Epic Structure

bash
1mkdir -p specs/epics/epic-name/references

Step 2: Create epic.md

markdown
1# [Epic Title]
2
3Brief description of what this epic encompasses.
4
5## Overview
6
7High-level goals and scope of this epic.
8
9## Key Features
10
111. Feature area 1
122. Feature area 2
133. Feature area 3
14
15## Related Issues
16
17| Issue | Title | Status |
18|-------|-------|--------|
19| task01-xxx | Description | pending |
20| task02-xxx | Description | pending |
21
22## Progress
23
24See [progress.md](progress.md) for sprint tracking.
25
26## References
27
28- [Design.md](references/Design.md) - Main design specification

Step 3: Create progress.md

markdown
1# [Epic Name] Progress
2
3## Current Status
4Brief status description.
5
6## In Progress
7- [ ] issue-id - Description
8
9## Completed Sprints
10
11### [Sprint Name]
12- [x] issue-id - Description
13
14#### [YYYY-MM-DD] Session #N
15- Working on: issue-id
16- Completed: F001, F002
17- Notes:
18  - What was done
19  - Decisions made

Step 4: Add Reference Documents

Copy or create reference documents in specs/epics/epic-name/references/:

• Design specifications
• Architecture diagrams
• API documentation
• Requirements documents

Step 5: Git Commit

bash
1git add specs/epics/epic-name/
2git commit -m "feat: create epic-name epic"

Updating an Epic

Adding Issues to Epic

Update the "Related Issues" table in epic.md:

markdown
1| Issue | Title | Status |
2|-------|-------|--------|
3| task01-xxx | Description | completed |
4| task02-xxx | Description | in-progress |
5| task03-xxx | New issue | pending |

Updating Progress

Add session entries to progress.md:

markdown
1#### [YYYY-MM-DD] Session #N
2- Working on: issue-id
3- Completed: F001, F002, F003
4- Commits: abc123
5- Notes:
6  - Brief description of work done

Adding References

Copy new reference documents to references/ and update epic.md:

markdown
1## References
2
3- [Design.md](references/Design.md) - Main design specification
4- [API.md](references/API.md) - API documentation

Rules

• Each Epic MUST have epic.md and progress.md
• Update issue status in epic.md when issues complete
• Log all sessions in progress.md
• Keep references organized and up-to-date