Hmans Beans
hmans-beans is a Claude Code plugin for the Build phase that connects Beans, a flat-file CLI issue tracker, so you and your agent can track work in the repo without a hosted PM database.
by hmans · github.com/hmans/beans
Run a git-friendly flat-file issue tracker from the CLI and wire Claude to configure, prime, and track work without Jira or a database.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install hmans-beans@hmans/beansBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:hmans/beans") and the paste-ready config with skillselion.get_install_config("plugin:hmans/beans").
What it does
hmans-beans is a Claude Code plugin around Beans, a CLI-based flat-file issue tracker built for humans and robots alike. Solo and indie builders who want issue history inside the repo—not another SaaS board—can list, create, and organize work from the terminal while keeping agents in sync through configure and prime style setup. It fits the Build phase when you are turning ideas into tickets and the Operate phase when you are iterating on bugs and chores, without standing up PostgreSQL or paying per seat. The bundle ships one plugin keyworded around beans, Claude, track, and configure, which makes it a productivity and PM adjunct rather than a full agile suite. If you already live in Claude Code and want issues that agents can read and update as files, this is a low-friction alternative to heavy PM tools.
Highlights
- CLI-first flat-file issue storage that stays in your repo
- Designed for both human operators and coding-agent workflows
- Claude-oriented configure and prime flows for agent-assisted tracking
- No hosted database—issues live as plain files you can diff and review
- Community plugin bundle with a single focused beans integration
Why builders use it
Hosted issue trackers and heavy PM stacks slow solo builders down and keep task state outside the codebase where agents cannot safely read or update it.
After you add the plugin and configure Beans, issues live as flat files in your project, trackable from the CLI and aligned with Claude-assisted prime and track workflows.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 663 stars, 0 votes.
FAQ
Who is hmans-beans for?
Solo builders and Claude Code users who want robot- and human-readable issues stored as files in git, not a separate PM product.
When should I use hmans-beans?
Use it when you start naming build tasks, bugs, and launch checklists during development and want that list to stay versioned with the repo through ship and iterate cycles.
How do I add hmans-beans to my agent?
Install the hmans/beans Claude Code plugin from the catalog, open your project in Claude Code, and follow the plugin’s configure and prime steps so Beans CLI commands and agent context stay in sync.
Comments
Share how you use hmans-beans, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.