Problem
Root AGENTS.md makes bd central to the contributor workflow ("Quick Reference", "Landing the Plane"), but .beads/config.yaml is mostly commented out and there's no integration with GitHub Issues, Linear, or any sync target. New contributors following AGENTS.md are sent to a tool that isn't actually wired up.
Decide one path
Option A — Use it. Configure .beads/config.yaml (sync branch, GitHub or Linear integration), document setup in CONTRIBUTING, and verify bd ready / bd sync actually work.
Option B — Remove it. Delete .beads/, strip the bd sections from AGENTS.md and CLAUDE.md, and replace with whatever the actual issue-tracking workflow is (likely GitHub Issues).
Acceptance criteria (for either option)
- A new contributor can follow
CONTRIBUTING.md end-to-end without hitting a tool that isn't configured.
- AGENTS.md instructions match the chosen path.
Problem
Root
AGENTS.mdmakesbdcentral to the contributor workflow ("Quick Reference", "Landing the Plane"), but.beads/config.yamlis mostly commented out and there's no integration with GitHub Issues, Linear, or any sync target. New contributors following AGENTS.md are sent to a tool that isn't actually wired up.Decide one path
Option A — Use it. Configure
.beads/config.yaml(sync branch, GitHub or Linear integration), document setup in CONTRIBUTING, and verifybd ready/bd syncactually work.Option B — Remove it. Delete
.beads/, strip the bd sections fromAGENTS.mdandCLAUDE.md, and replace with whatever the actual issue-tracking workflow is (likely GitHub Issues).Acceptance criteria (for either option)
CONTRIBUTING.mdend-to-end without hitting a tool that isn't configured.