Skip to main content

Epics

An epic is a task too large for one runner. Jaah never works on it directly: it splits the epic into subtasks and runs them in stages. Analyze pins down the requirements, Design chooses the approach, Plan divides the work into build subtasks, each Coder subtask delivers one merged change, and Finish checks the result as a whole. A stage starts only when the stages before it are done, and each subtask runs like an ordinary task, in its own worktree, with its own state, cost and outcome.

You choose how involved to be when you start it: Unattended lets every stage decide for itself, while Guided has Analyze and Design ask you before they settle the requirements and the design.

An epic has no runner of its own, so its state follows its subtasks: Running while any of them has work to do, Asking while one waits for your answer, Failed when one has used all its attempts, and Done once every subtask is done. A subtask's question goes to the person it or its epic is assigned to, else to whoever created it, as for any task; see Answer a task's question.

An epic is not a feature. A feature only groups related tasks inside a project and never runs anything; an epic can sit in a feature like any other task. The ideas behind both are in How epics and features work.

Grouping tasks is covered in Organize tasks into features, and the Subtasks tab is described in Task page.