bip.epic

Scan clones, EPIC issues, and GitHub activity to orchestrate multi-clone workflows.

29|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/matsen/bipartite --skill bip-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bip.epic
Source: https://github.com/matsen/bipartite/tree/main/skills/bip.epic
Command: npx skills add https://github.com/matsen/bipartite --skill bip-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams initialize and monitor EPIC-based multi-clone workflows by providing a unified dashboard that scans clones, EPIC issues, and GitHub activity to establish operational context.

Core Features & Use Cases

  • Discover and load configuration via .epic-config.json to coordinate clones and worktrees.
  • Scan EPIC issues, track clone status, and surface ready-to-spawn work.
  • Orchestrate spawning and status updates using /bip.epic.spawn and /bip.epic.poll.

Quick Start

Create a .epic-config.json with your clone layout and repository details, then run bip epic to initialize the dashboard.

Frequently Asked Questions about bip.epic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate multi-clone GitHub workflows across multiple repositories?

Multi-clone orchestration coordinates clones and EPIC issues by scanning GitHub activity to establish operational context. It uses a configuration file to track clone status and surface ready-to-spawn work across repositories.

What is an EPIC issue dashboard for multi-clone development?

An EPIC issue dashboard provides unified visibility into active work and ready-to-spawn tasks by scanning clones, EPIC issues, and GitHub activity. It applies to session-start contexts and mid-session updates for cross-repo coordination.

How do I configure EPIC multi-clone tracking using a JSON config file?

Create a .epic-config.json file defining your clone layout and repository details, then run the dashboard initialization to load the configuration and coordinate clones and worktrees for EPIC tracking.

Do I need the gh CLI to track GitHub EPIC issues across clones?

Yes, access to GitHub via the gh command-line tool is required to scan EPIC issues and GitHub activity. A conductor capable of cross-repo coordination is also needed to orchestrate the workflow.

Can I use tmux for cross-repo orchestration when managing multiple clones?

Yes, tmux is supported as a keyword for orchestrating EPIC multi-clone workflows. It functions alongside the dashboard to manage session contexts and coordinate active work across repositories.