Reeds
Run autonomous multi-task dev loops that pull the next Beads-tracked issue and keep an agent executing until the queue is clear.
Overview
reeds is a plugin marketplace for the Build phase that adds Ralph Loop autonomous execution on top of Beads issue tracking.
What is this marketplace?
- Ralph Loop + Beads issue-tracking integration for hands-off task chains
- Autonomous multi-task development loops aimed at CI/CD-friendly workflows
- MIT-licensed single-plugin marketplace (reeds v0.1.0)
- Keywords cover ralph-loop, beads, task-management, and workflow automation
- Marketplace lists 1 plugin (reeds v0.1.0)
- MIT license on the bundled plugin
What problem does it solve?
Manually feeding the next ticket to your coding agent breaks flow and wastes context when you already track work in Beads.
Who is it for?
Indie builders running Beads (or similar issue queues) who want Ralph Loop-style autonomous passes over a defined backlog.
Skip if: One-off feature prompts with no issue tracker or teams that forbid autonomous multi-step agent runs in CI.
What do I get? / Deliverables
After you register reeds, your agent can run multi-task loops that consume Beads issues continuously instead of one prompt per task.
- Installed reeds marketplace plugin (1 plugin bundle)
- Configured Ralph Loop + Beads execution path for your backlog
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Continuous Ralph-style execution lives in the build shelf because it turns a backlog into shipped work, not one-off codegen. PM is the canonical home for issue-tracker-driven execution and loop orchestration across many tasks.
How it compares
Workflow automation marketplace plugin, not a single static skill file.
Common Questions / FAQ
Who is Reeds for?
Solo and indie developers who track tasks in Beads and want Claude Code to execute many issues in a Ralph Loop without constant hand-holding.
When should I use Reeds?
Use it when you have a prioritized Beads queue and want continuous agent-driven implementation between your normal reviews and merges.
How do I add Reeds to my agent?
Add the rikdc/Reeds Claude marketplace to Claude Code, install the Reeds plugin from the manifest, and point it at your Beads-backed project per the repo README on GitHub.