Integration with Beads

[tlvenn]

I am wondering if https://github.com/steveyegge/beads could not add additional value if it was integrated to replace text / md todos and issues.
A plan could map to an epic and any work after that could be a task / sub-task.

[tlvenn]

This recent fork to keep beads simple might be a better fit for the integration

https://github.com/Dicklesworthstone/beads_rust

[tlvenn]

Another avenue to explore maybe if bead philosophy (maintaining a sqlite db) is not appealing is to leverage something like

https://github.com/wedow/ticket

But this is probably pretty similar to the existing file-todos skill...

[tmchow]

I love the idea of using Beads Rust port. I like it because it never does auto git operations, it's always explicit. So it shed all the auto-commit and hooks that were causing me grief in using the main beads project.

The slimmed down nature probably makes it perfect for Every's compound engineering.

[dirkkok101]

I would love to use beads (the rust version) with this plugin. It's what is putting me off using other people's frameworks, because having beads as the planning and execution harness is so powerful.

[kieranklaassen]

You can! I used it with beads! Nothing holding you back. Just install beads and off you go. If you want the plan to fully live in beads you can just say to use beads instead of a markdown fie in CLAUDE.md. I used it and works

[tmchow]

Problem I've found with the beads-rust port is the lack of automatic commits of the beads files. Having a heck of a time figuring out the right workflow.

Irony is I didn't like the main beads project because of how intrusive all the git hooks integrations was. Oh the irony.

[whw]

Haha I feel this - neither one feels exactly right