claude

fleet-epic

Task design pages (/fleet-task-plan); old EPIC commands explain their retirement. Optional, never installed by migration.

2 on GitHubby verkyyiv0.5.0MITupdated yesterday
/

Plugin fleet-epic from marketplace claude-fleet in verkyyi/claude-fleet. Commands read from the repo's manifest — yesterday.

What it installs

Skills (1)

  • epic-page

    Shared HTML frame for an ordinary Task's design and implementation evidence. Use with /fleet-task-plan. The historical epic-page name remains for existing pages; it creates no EPIC, batch, parent task or driver.

Slash commands (4)

  • /fleet-epic:fleet-epic-plan

    Retired EPIC entrypoint — use one ordinary Task and its native Agent.

  • /fleet-epic:fleet-epic-report

    Retired EPIC entrypoint — use one ordinary Task and its native Agent.

  • /fleet-epic:fleet-epic-run

    Retired EPIC entrypoint — use one ordinary Task and its native Agent.

  • /fleet-epic:fleet-task-plan

    Design one ordinary Task — explain the problem, intended behavior, implementation and acceptance on a shared page.

Subagents (1)

  • epic-driver

    Retired Fleet role; retained for one version to explain migration.

View source on GitHub

More from verkyyi/claude-fleet

All 4 plugins →

fleet

claude

The fleet slash commands, base skills, and hooks.

5 skills · 10 commands

2

For the machine and hub admins only: runbooks as skills — prepare and enroll a Mac, logins, a cloud Linux node, an overseas relay, hub deploy, release rules, incident runbooks, reading the doctor. Never installed by default, never handed out by the hub.

11 skills

2

Web pages a session opens show on your computer; an OAuth callback to localhost is forwarded back over your ssh (MCP authorization, /login). Off unless installed.

1 skill · hooks

2

Maintain fleet-epic?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins4 plugins