🎯

ln-210-epic-coordinator

🎯Skill

from levnikolaevich/claude-code-skills

VibeIndex|
What it does

Coordinates epic creation and replanning by decomposing scope into 3-7 logical domains with auto-discovery of team details.

πŸ“¦

Part of

levnikolaevich/claude-code-skills(85 items)

ln-210-epic-coordinator

Installation

Claude CodeAdd plugin in Claude Code
/plugin add levnikolaevich/claude-code-skills
git cloneClone repository
git clone https://github.com/levnikolaevich/claude-code-skills.git ~/.claude/skills
πŸ“– Extracted from docs: levnikolaevich/claude-code-skills
13Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

CREATE/REPLAN Epics from scope (3-7 Epics). Batch Preview + Auto-extraction. Decompose-First Pattern. Auto-discovers team ID.

Overview

# Epic Coordinator

Universal Epic management coordinator that handles both creation and replanning through scope decomposition.

When to Use This Skill

This skill should be used when:

  • Start new scope/initiative requiring decomposition into multiple logical domains (CREATE mode)
  • Break down large architectural requirement into Epics
  • Update existing Epics when scope/requirements change (REPLAN mode)
  • Rebalance Epic scopes within an initiative
  • Add new Epics to existing initiative structure
  • First step in project planning (scope β†’ Epics β†’ Stories β†’ Tasks)
  • Define clear scope boundaries and success criteria for each domain

Output: 3-7 Linear Projects (logical domains/modules)

Core Concepts

Decompose-First Pattern

Key principle: ALWAYS analyze scope and build IDEAL Epic plan FIRST, THEN check existing Epics to determine mode:

  • No existing Epics β†’ CREATE MODE (generate and create all Epics)
  • Has existing Epics β†’ REPLAN MODE (compare, determine operations: KEEP/UPDATE/OBSOLETE/CREATE)

Rationale: Ensures consistent Epic decomposition based on current scope requirements, independent of existing Epic structure (which may be outdated or suboptimal).

Epic 0 Reserved for Infrastructure

Rule: Epic 0 is a reserved index for Infrastructure Epic within an initiative.

When to use Epic 0:

  • New project requiring infrastructure setup
  • Multi-stack project (Frontend + Backend on different stacks)
  • Project with security/monitoring/deployment requirements

Epic indexes within initiative:

  • Epic 0: Infrastructure & Operations (if needed)
  • Epic 1, 2, 3, ... N: Business domains

Linear Project Titles:

  • Use Next Epic Number from kanban_board.md for sequential numbering
  • Example: Next Epic Number = 11

- Epic 0 β†’ Linear title: "Epic 11: Infrastructure & Operations"

- Epic 1 β†’ Linear title: "Epic 12: User Management"

- Epic 2 β†’ Linear title: "Epic 13: Product Catalog"

Important: Epic 0/1/2 are initiative-internal indexes for organizing domains. Linear uses global Next Epic Number for project titles.

---

Workflow

Phase 1: Discovery & Research

Objective: Gather all necessary context before Epic decomposition.

Step 1: Load Configuration

Auto-discovers Team ID and Next Epic Number from docs/tasks/kanban_board.md:

  • Team ID: Reads Linear Configuration table β†’ Fallback: Ask user directly
  • Next Epic Number: Reads Next Epic Number field β†’ Fallback: Ask user directly

Details: See CLAUDE.md sections "Configuration Auto-Discovery" and "Linear Integration".

Step 2: Project Research

Objective: Research project documentation AND frontend code to understand context BEFORE asking user questions.

Process:

  1. Document Scan:

- Use Glob to find: docs/requirements.md, docs/architecture.md, docs/tech_stack.md

- Use Read to load found documents

  1. Frontend Code Scan (if applicable):

- Use Glob to find: */.html, src/*/.html, public/*/.html, templates/*/.html

- Use Read to load HTML files

- Extract functional domains from:

- Navigation menus: