Add native Beads integration as long‑term memory backend

[russosalv]

Hi,
I’d like to propose a native integration between BMAD-METHOD and Beads (github.com/steveyegge/beads). Beads is a git-backed, agent-first issue tracker and memory system that lets AI agents persist and query decisions, dependencies and “ready work” directly inside the repo.​

For BMAD this could act as a long-term memory layer that complements PRD/Architecture/Story files by:

Storing retro decisions in a structured, queryable way (per sprint, domain, priority), so SM/Dev agents can actually reuse those decisions in future stories instead of forgetting them.

Tracking recurring frontend/backend bugs and canonical fixes, giving Dev agents a concrete place to look for “how we solved this last time” and which patterns the team agreed to standardize.

Providing a cross-sprint memory of process and architecture choices linked to the same git repo, instead of scattering them across ad-hoc docs.

The idea is not to replace BMAD’s workflow, but to give BMAD agents a first-class, repo-local memory graph they can read/write to when planning, implementing and refining work. In my experience this would significantly reduce repeated mistakes and help agents stay aligned with previous decisions over many sprints.

Would you consider adding official support or at least documenting a recommended way to use BMAD together with Beads as a long-term memory backend?

[ozenalp22]

I added on my fork of 6.0alpha if you want to try it out
https://github.com/ozenalp22/bmad-withbeads