rai-epic-start

To initialize a new epic, the system creates a standardized epic directory, generates a brief and scope from epic templates, and registers the entry in your backlog tracker to ensure consistent project setup.

Scaffolding an epic brief and scope is handled by generating standardized files from epic templates, enforcing artifact creation and branch verification steps to reduce manual setup friction for new project epics.

Branch verification enforces a required git branch check before initializing an epic directory, ensuring your repository state is correct before creating artifacts and registering the tracker entry.

Yes, epic templates support initializing new epics sized for three to ten stories, generating the required brief, scope, and tracker metadata for small to medium project batches.

Collision checks prevent duplicate epic artifacts by verifying existing directory and tracker entries before creation, stopping the initialization process to avoid overwriting existing project management data.

A git repository is required because the initialization process enforces branch verification steps before creating the epic directory, brief, and tracker entry to maintain project consistency.