name	epic
description	Create a new epic using Saga's 8-part structure
user-invocable	true
context	fork
agent	saga-epic-creator
argument-hint	[epic title or topic]
allowed-tools	Read, Glob, Grep, Write, Edit

Create a new epic for: $ARGUMENTS

Use the Saga persona's 8-part structure from thestudioarc/personas/saga-epic-creator.md:

Title — Outcome-focused, not task-focused
Narrative — The user/business problem and why it matters now
References — Research, personas, OKRs, discovery artifacts
Acceptance Criteria — High-level, testable at epic scale (not story-level)
Constraints & Non-Goals — What's out of scope, regulatory limits, tech boundaries
Stakeholders & Roles — Owner, design, tech lead, QA, external parties
Success Metrics — Adoption, activation, time-to-value, revenue impact
Context & Assumptions — Business rules, dependencies, systems affected

The epic must be AI-ready: implementable by Claude/Cursor without guessing scope. After writing, flag that it needs Meridian review before commit.

Más de este repositorio

mismo repositorio

Manage shared project memory for cross-session knowledge persistence. 33 actions: save, search, federation, profiles, Hive, and more.

Manage shared project memory for cross-session knowledge persistence. 33 actions: save, search, federation, profiles, Hive, and more.

Execute one Ralph development loop iteration. Reads fix_plan.md, implements the first unchecked task, verifies, and commits.

Review open epics and create a Helm session plan with Meridian review

Generate a standardized evidence comment for a PR

Build a structured Intent Specification for a task

name	epic
description	Create a new epic using Saga's 8-part structure
user-invocable	true
context	fork
agent	saga-epic-creator
argument-hint	[epic title or topic]
allowed-tools	Read, Glob, Grep, Write, Edit

Create a new epic for: $ARGUMENTS

Use the Saga persona's 8-part structure from thestudioarc/personas/saga-epic-creator.md:

Title — Outcome-focused, not task-focused
Narrative — The user/business problem and why it matters now
References — Research, personas, OKRs, discovery artifacts
Acceptance Criteria — High-level, testable at epic scale (not story-level)
Constraints & Non-Goals — What's out of scope, regulatory limits, tech boundaries
Stakeholders & Roles — Owner, design, tech lead, QA, external parties
Success Metrics — Adoption, activation, time-to-value, revenue impact
Context & Assumptions — Business rules, dependencies, systems affected

The epic must be AI-ready: implementable by Claude/Cursor without guessing scope. After writing, flag that it needs Meridian review before commit.