How do I install the Jb Beans skill?

Run npx skillmds@latest add bjesuiter/jb-beans in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jb Beans safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jb Beans?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jb Beans free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jb Beans?

bjesuiter (@bjesuiter) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jb Beans by bjesuiter — Agent Skill

Name: Jb Beans
Author: bjesuiter

File contents

Beans

Use beans to manage Git-friendly Markdown issues stored in .beans/.

Start with project guidance

Before working in a Beans-enabled repository, run:

beans prime

Follow its output. It defines the repository's workflow, issue model, statuses, and agent expectations and takes precedence over generic guidance here.

Installation and binary safety

Install the Go CLI through Homebrew or Go:

brew install hmans/beans/beans
# or
go install github.com/hmans/beans@latest

Never install beans with npm or Bun. The package with that name is an unrelated legacy Node program. If Beans fails unexpectedly, especially with a coffee-script module error, diagnose command shadowing:

which -a beans
beans version

Use an absolute path to the working Homebrew or Go binary when necessary, then leave broader PATH repair outside the task.

Agent workflow

Prefer --json whenever a command supports it. A typical lifecycle is:

# Discover actionable or existing work
beans list --json --ready
beans list --json -S "login"
beans show --json <id>

# Create and start work
beans create --json "Add login screen" -t feature -s todo -d "Build the initial login UI"
beans update --json <id> -s in-progress

# Record useful progress
beans update --json <id> --body-append "## Notes\n\nStarted implementation"

# Complete with a durable summary
beans update --json <id> -s completed \
  --body-append "## Summary of Changes\n\nImplemented and validated the feature."

Keep issue bodies current with reproduction details, decisions, checklists, progress, and final summaries. Use structured parent/blocking relationships instead of duplicating dependencies only in prose.

Use narrow body replacements or --if-match updates when concurrent edits could otherwise overwrite content. Run beans check after substantial configuration or relationship changes. Archive work only when the project workflow or user requests it.

Discover current commands

Do not rely on a copied command catalog. Inspect the installed CLI because supported fields and flags can change:

beans --help
beans <command> --help
beans version

For advanced filtering and relationship traversal, inspect beans graphql --help and beans graphql --schema. Beans has no built-in beans tui; use the separate beans-tui tool when requested.

Project: https://github.com/hmans/beans

---name: jb-beansdescription: Use when a repository contains `.beans/` or the user mentions Beans, beans prime, flat-file issues, task tracking, or issue status changes.---# BeansUse `beans` to manage Git-friendly Markdown issues stored in `.beans/`.## Start with project guidanceBefore working in a Beans-enabled repository, run:```bashbeans prime```Follow its output. It defines the repository's workflow, issue model, statuses, and agent expectations and takes precedence over generic guidance here.## Installation and binary safetyInstall the Go CLI through Homebrew or Go:```bashbrew install hmans/beans/beans# orgo install github.com/hmans/beans@latest```Never install `beans` with npm or Bun. The package with that name is an unrelated legacy Node program. If Beans fails unexpectedly, especially with a `coffee-script` module error, diagnose command shadowing:```bashwhich -a beansbeans version```Use an absolute path to the working Homebrew or Go binary when necessary, then leave broader PATH repair outside the task.## Agent workflowPrefer `--json` whenever a command supports it. A typical lifecycle is:```bash# Discover actionable or existing workbeans list --json --readybeans list --json -S "login"beans show --json <id># Create and start workbeans create --json "Add login screen" -t feature -s todo -d "Build the initial login UI"beans update --json <id> -s in-progress# Record useful progressbeans update --json <id> --body-append "## Notes\n\nStarted implementation"# Complete with a durable summarybeans update --json <id> -s completed \ --body-append "## Summary of Changes\n\nImplemented and validated the feature."```Keep issue bodies current with reproduction details, decisions, checklists, progress, and final summaries. Use structured parent/blocking relationships instead of duplicating dependencies only in prose.Use narrow body replacements or `--if-match` updates when concurrent edits could otherwise overwrite content. Run `beans check` after substantial configuration or relationship changes. Archive work only when the project workflow or user requests it.## Discover current commandsDo not rely on a copied command catalog. Inspect the installed CLI because supported fields and flags can change:```bashbeans --helpbeans <command> --helpbeans version```For advanced filtering and relationship traversal, inspect `beans graphql --help` and `beans graphql --schema`. Beans has no built-in `beans tui`; use the separate `beans-tui` tool when requested.Project: https://github.com/hmans/beans

Frequently asked questions

Jb Beans