bmad-story-cycle

Full epic development cycle: all stories implemented, verified, reviewed, and merged in sequence. Use when user says "dev epic N", "run story cycle", "implement epic [N]", or "story cycle [N.M]" to resume from a specific story.

The World's First Agentic IDE. Visual dashboard: live sessions, task management, code editor, terminal. Epic Swarm parallel workflows. Auto-proceed rules. Automation patterns. Beads + Agent Mail + 50 bash tools. Supervise 20+ agents from one UI.

Gtm Alpha Consultant

Professional GTM consultation using EPIC framework for strategic go-to-market advice.

Epic Run

create-task-files

Export tasks from TodoWrite or feature plans into structured markdown files (epic, user-story, bug, issue) in a tasks/ directory. Use when the user wants to create task files, export tasks, track work in files, or mentions "create tasks", "export", "epic", "user story".

Io.Github.Toolwright Adk/Linear Bootstrap

Bootstrap Linear projects from natural language — milestones, epics, issues, and dependencies.

epic-auth

Guide on authentication, sessions, OAuth, 2FA, and passkeys for Epic Stack

ralph-tui-create-beads

Convert PRDs to beads for ralph-tui execution. Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with beads as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads.

Langcare Mcp Fhir

An MCP FHIR server written in Go for EMR systems like Epic and Cerner

ccpm

CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress — even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue/PR operations with no delivery context.

epic

Create and manage Epics - collections of related issues for major feature areas. Use when starting a new project(big feature), organizing work into themes, or adding reference documents.