epic-workflow

Plugin epic-workflow from marketplace peakflames-plugins in peakflames/claude-plugins-peakflames. Commands read from the repo's manifest — 2 days ago.

Skills (12)

• add

  Adds new epic(s) to the implementation plan from natural language description. Use when the user wants to add a single epic or small batch without re-running full planning. Triggers on: "add epic", "new epic", "create epic", "I need to add more work", "there's a new feature we need", "can we squeeze

• discover

  Adaptive discovery interview that produces product-vision.md and concept-of-operations.md. Use when starting a new project (greenfield) or evolving an existing project's direction (brownfield). Triggers on: "discover", "new project", "product vision", "concept of operations", "what should we build",

• migrate-2.5

  One-shot migration from the pre-v2.5.0 implementation-plan layout (single index.md with status table) to the v2.5.0 layout (per-phase index files + per-epic status sidecars). Run once per project after upgrading to epic-workflow v2.5.0. Triggers on: "migrate to 2.5", "upgrade implementation plan", "

• pause

  Pauses current epic implementation and saves progress to a handoff file. Use when stopping mid-epic before the session ends. Triggers on: "pause epic", "stop epic", "save progress", "I need to stop for today", "save my progress", "I'm done for now", "let's pick this up later". Note: If the user says

• plan-project

  Derives implementation plan (phases, epics, specs) from vision and ConOps documents. Use after /epic-workflow:discover or when the user wants to create an implementation plan from existing vision docs. Triggers on: "plan project", "create epics", "implementation plan", "derive epics", "break this in

• quick-fix

  Lightweight path for trivial items — bugs, copy changes, small enhancements (~2 hours or less). Creates a `hotfix/` branch, plans and implements the fix with applicable quality gates, and ships via prompted solo mode (local merge) or team mode (push + `gh pr create`). Quick-fixes are commit-level re

• refresh-docs

  Refreshes architecture.md and design-notes.md to match the as-built codebase by reading source files and session handoffs. Use after completing a phase or before a release. Triggers on: "refresh docs", "update architecture", "sync documentation", "docs are stale", "docs are out of date", "architectu

• setup

  Audits CLAUDE.md for required sections and stubs architecture.md and design-notes.md. Use for first-time project setup before starting epics. Triggers on: "setup project", "audit CLAUDE.md", "project setup", "prepare project for epics", "initialize project", "first time setup", "configure CLAUDE.md"

• start

  Implements an epic — loads spec, plans, implements, and verifies against acceptance criteria. Use when the user wants to begin or resume working on a specific epic number. Triggers on: "start epic", "implement epic", "begin epic", "work on epic", "let's work on epic N", "pick up epic N", "resume epi

• status

  Displays a project status dashboard — epic progress, active work, stale paused epics, and next actions. Strictly read-only — does not modify any files. Triggers on: "status", "project status", "what's the progress", "how far along are we", "show me the dashboard", "where are we", "what's left to do"

• triage

  Advisory routing for an incoming GitHub issue or ad-hoc request — sizes the request against product vision and ConOps, then recommends one of HEAVY / EPIC / TRIVIAL. On user confirm, dispatches `/add` or `/quick-fix` in-session via the Skill tool; for HEAVY outcomes, prints the commands to run in a

• wrapup

  Independent verification review of a completed epic — verifies implementation, closes out, and orients to next steps. Use after an epic is implemented and needs independent review. Triggers on: "wrapup epic", "verify epic", "review epic", "close epic", "is epic N done?", "check my work on epic N", "