Skip to main content
Both the marketplace and the plugin are named builddown. Installing gives you all eight bd- skills — see BuildDown skills for what each one does.
You need Claude Code installed and working. Everything below runs through its plugin manager.

​
Installation

1

Add and install the plugin

The plugin manager accepts two command forms:
  • claude plugin … — works in the Claude Code app or a terminal, and is the form to use in scripts.
  • /plugin … — the slash form, available in the Claude Code CLI. Some options exist only here.
Add the marketplace, then install the plugin from it:
With no branch or tag appended, this gives you the stable channel — the most recent released version. Append @testing instead to track ongoing development.Both channels are covered in Versions and channels below.
2

Load the skills

Run /reload-plugins to activate the plugin in your current session. Restarting Claude Code also works, but is heavier than necessary.The bd- skills aren’t available until you do one or the other.
3

Verify plugin registration

Confirm the plugin is registered:
builddown appears in the list, and the bd- skills are available in your session.

​
Versions and channels

Which version you get depends on how you added the marketplace: Stable changes only when a new version ships. Development follows testing and can change at any time, including in ways that haven’t been through a release.
Two separate references decide what you end up with. The marketplace reference picks which catalog you read; the catalog then names which version of the skills to install. On the stable channel the catalog pins that to the release tag, which is why refreshing the marketplace doesn’t move your skills until a new version is out.

​
Check which version you have

The slash form also accepts a state filter, which the terminal form does not:

​
Move between channels

Your channel is recorded on your machine when you first add the marketplace. A new release cannot move you — switching is something you do locally. To move from development to stable:
Append @testing to the middle command to go the other way.
Removing a marketplace uninstalls every plugin installed from it. The third command is not optional — without it you are left with no skills installed.

​
Updating

Refresh the marketplace, update the plugin, then reload:
Then run /reload-plugins. What this actually picks up depends on your channel. On stable you move only if a new version has been released; running it between releases is a no-op. On development you get whatever has landed on testing since you last updated.
Third-party marketplaces have automatic updates switched off by default. You can turn it on per marketplace from the Marketplaces tab of /plugin if you would rather not update by hand.

​
Install without the plugin system

If you would rather not use the plugin manager, the repository ships an install script:
By default this symlinks the skills into ~/.claude/skills/, so a later git pull updates them immediately. To pin a specific release instead of tracking a checkout:

​
Next step

With the skills installed, set up your project so the bd- skills know where your issues and repo live.

Project setup

Point the BuildDown skills at your tracker and repository.