> ## Documentation Index
> Fetch the complete documentation index at: https://docs.builddown.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Install BuildDown skills

> Install the BuildDown plugin for Claude Code — a suite of planning-time skills that help you shape issues before AI-Implement turns them into pull requests.

Both the marketplace and the plugin are named `builddown`. Installing gives you all eight `bd-` skills — see [BuildDown skills](/skills/introduction) for what each one does.

<Note>
  You need [Claude Code](https://docs.claude.com/en/docs/claude-code) installed and working. Everything below runs through its plugin manager.
</Note>

## Installation

<Steps>
  <Step title="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:

    ```bash theme={null}
    claude plugin marketplace add BuildDownAI/skills
    claude plugin install builddown@builddown
    ```

    <Info>
      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](#versions-and-channels) below.
    </Info>
  </Step>

  <Step title="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.
  </Step>

  <Step title="Verify plugin registration">
    Confirm the plugin is registered:

    ```bash theme={null}
    claude plugin list
    ```

    <Check>
      `builddown` appears in the list, and the `bd-` skills are available in your session.
    </Check>
  </Step>
</Steps>

## Versions and channels

Which version you get depends on how you added the marketplace:

| How you added it                       | Channel         | What you get                                                 |
| -------------------------------------- | --------------- | ------------------------------------------------------------ |
| `BuildDownAI/skills` (no ref)          | **Stable**      | the most recent released version — currently `1.0.0`         |
| `BuildDownAI/skills@testing`           | **Development** | whatever has landed on the `testing` branch, released or not |
| `./install.sh --from-git <url>@v1.0.0` | pinned          | exactly that tag, without using the plugin system            |
| `./install.sh` from a local checkout   | unversioned     | whatever that checkout happens to contain                    |

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.

<Note>
  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.
</Note>

### Check which version you have

```bash theme={null}
claude plugin list
```

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

```
/plugin list --enabled
```

### 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:

```bash theme={null}
claude plugin marketplace remove builddown
claude plugin marketplace add BuildDownAI/skills
claude plugin install builddown@builddown
```

Append `@testing` to the middle command to go the other way.

<Warning>
  Removing a marketplace uninstalls every plugin installed from it. The third command is not optional — without it you are left with no skills installed.
</Warning>

## Updating

Refresh the marketplace, update the plugin, then reload:

```bash theme={null}
claude plugin marketplace update builddown
claude plugin update builddown
```

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.

<Tip>
  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.
</Tip>

## Install without the plugin system

If you would rather not use the plugin manager, the repository ships an install script:

```bash theme={null}
git clone https://github.com/BuildDownAI/skills.git builddown-skills
cd builddown-skills
./install.sh
```

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:

```bash theme={null}
./install.sh --from-git https://github.com/BuildDownAI/skills.git@v1.0.0
```

## Next step

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

<Card title="Project setup" icon="folder-gear" href="/skills/project-setup">
  Point the BuildDown skills at your tracker and repository.
</Card>