mcpField
E
epic-tracker

epic-tracker

github.com/adeonirDevelopment890 installsUpdated 1d ago
Repository

About epic-tracker

Epic Tracker is a skill for managing delivery work in Linear or GitHub, from roadmap decomposition to epics, stories, bugs, and status updates. It drafts artifacts for approval before creating them in the configured tracker.

Key features

  1. 01Decomposes PRDs into roadmap plans
  2. 02Creates epics, stories, and bugs
  3. 03Drafts artifacts for approval
  4. 04Updates status and dependencies
  5. 05Keeps tracker as source of truth

Use cases

  1. 01Turning a PRD into approved epics
  2. 02Creating a story or bug report
  3. 03Updating work status or dependencies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/adeonir/agent-skills --skill epic-tracker

After installing, type/epic-trackerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
agents/
openai.yaml
instructions/
bug.md
decompose.md
epic.md
feature.md
story.md
sync.md
references/
ac-validation.md
artifact-content.md
derivation.md
ice-scoring.md
roadmap.md
tracker.md

Details

From the project README

Epic Tracker

Manages the delivery lifecycle in an external tracker. Plan epics, track stories, and report bugs — every artifact lives in Linear or GitHub, which is the single source of truth.

Triggers

  • Feature source ("create from this feature design doc", "create from this feature PRD", "turn this feature design doc into issues", "track this feature") → feature.md
  • Plan / decompose ("create roadmap", "plan the roadmap", "organize epics", "roadmap the PRD", "decompose", "break down the roadmap", "break this epic into stories", "create the epics from the roadmap") → decompose.md
  • Epic ("create epic", "new epic", "edit epic") → epic.md
  • Story ("create story", "new story", "add story", "edit story", "update story", "change story", "create task", "create chore") → story.md
  • Bug ("create bug", "report bug", "bug report", "edit bug") → bug.md
  • Status / overview ("mark done", "cancel this", "won't fix", "list epics", "what's in progress", "update status") → sync.md
  • Reparent ("move this to epic X", "reparent this story", "change the parent epic") → sync.md
  • Dependencies ("block this on X", "unblock this", "this depends on X") → sync.md

Workflow

flowchart TD
    DE[decompose] -->|plan| CR[create ref]
    FE[feature] -->|size| CR
    UR[user request] --> CR
    CR --> out[the tracker]

Every artifact takes the same path: a create ref drafts it and dispatches it to the tracker. decompose derives the plan from the project PRD, shows it as a draft in the chat, and creates the epics after the user approves it. When the user asks for a roadmap file, it writes docs/product/ROADMAP.md after that approval; a user who asks for only the roadmap gets it with nothing created. feature sizes a feature PRD or feature design doc into an epic or a standalone story, shows it as a draft in the chat, creates it after the user approves it, and writes no roadmap. A user request goes straight to the create ref, with no derivation. A configured tracker is required for tracker operations; report missing access without configuring the integration.

Comments

Markdown supported