Skip to main content
An epic is the top-level grouping of work. Every epic lives in its own directory under .tiny-brain/, and contains exactly one epic.md file.

Required structure

Required fields

See Frontmatter for the full reference.

Optional sections

The CLI’s nt new epic template includes a few sections that are useful but not parsed:
  • ## Target Audience — who benefits
  • ## Release Criteria — gate for declaring the epic done
  • ## Success Metrics — how you’ll measure it landed
  • ## Constraints and Dependencies — what could derail it
These render in the dashboard’s epic detail view but don’t drive any projection. Write them for humans.

What epics don’t have

  • No phase — epics don’t have a phase; the dashboard rolls it up from the features and fixes inside.
  • No assignee — epics aren’t assigned. Features and fixes are.
  • No ## Tasks — task lists belong on features and fixes. If you find yourself wanting tasks on an epic, you’re describing a feature.

See also