rai-epic-start

Create an epic branch from development and record an initial scope commit.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/fcastrillo/carbtrack-ai --skill rai-epic-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rai-epic-start
Source: https://github.com/fcastrillo/carbtrack-ai/tree/main/.claude/skills/rai-epic-start
Command: npx skills add https://github.com/fcastrillo/carbtrack-ai --skill rai-epic-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize and manage epic workflows by creating a dedicated epic branch from development and establishing an initial scope commit, enabling isolation and structured progression for multi-feature initiatives.

Core Features & Use Cases

  • Creates a new epic branch from the project's development branch (from {dev_branch}).
  • Establishes an initial scope commit documenting objectives, in-scope and out-of-scope items, and planned features.
  • Emits telemetry to track epic lifecycle events and readiness for the next design phase.
  • Provides a standardized lifecycle flow from epic start to epic design and eventual merge back to development. Example: When starting a new epic like E14, the skill configures epic/e14/{name} and lays groundwork for subsequent stories and features.

Quick Start

Initialize epic/e{N}/{epic-slug} from {dev_branch} and record the initial scope commit.

Frequently Asked Questions about rai-epic-start

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

FAQPage Schema
How do I start an epic branch from development in Git for agile project management?

To start an epic branch, you create a dedicated branch like epic/e14/{name} directly from your development baseline and establish an initial scope commit documenting objectives, in-scope items, out-of-scope items, and planned features.

What is an initial scope commit and why is it needed when isolating large bodies of work?

An initial scope commit is a foundational record created on a new epic branch that documents the epic's objectives, in-scope items, out-of-scope items, and planned features to enable structured progression and isolation for multi-feature initiatives.

Does this epic branching workflow require any specific Git workflow dependencies?

No specific dependencies are required to launch an epic with a dedicated branch and initial scope. The workflow operates independently to isolate large bodies of work and emit telemetry for lifecycle tracking from your existing development branch.

What's the best way to structure epic branches for future feature nesting in software engineering?

The best way to structure epic branches is using an epic/e{N}/{epic-slug} naming convention launched from your development branch, which lays the groundwork for subsequent stories and features to nest within the isolated epic workflow.

How does epic lifecycle tracking and telemetry work after creating an epic branch?

Epic lifecycle tracking emits telemetry events when the epic branch is created and the scope commit is established, monitoring readiness for the next design phase and eventual merge back to the development branch.

Can I use this epic branching approach for multi-feature initiatives with complex scope boundaries?

Yes, this approach is designed for multi-feature initiatives, providing isolation by creating a dedicated epic branch from development and explicitly documenting in-scope and out-of-scope items to manage complex scope boundaries.