Skip to main content
A fix is a bug fix tracked the same way features are. Fixes live next to their epic’s epic.md:
The shape is identical to a feature — same task list contract, same frontmatter base — with two differences: a severity field and a ## Reproduction Steps section.

Required structure

Required fields

Severity

severity is the one field that’s required on fixes but not on features. The values are deliberately coarse — four levels is enough to triage, more just invites bikeshedding: Not parsed but expected by reviewers. A reproducible bug closes faster than one described as “sometimes the login doesn’t work”. The dashboard surfaces this section verbatim on the fix page.

Root Cause (optional)

Filled in once the fix is found. Useful for postmortems and for future-you when the same area breaks again.

See also