---
name: setup
description: Use first for install/update routing — sends setup, doctor, or MCP requests to the correct TAP setup flow
level: 2
---

# Setup

Use `/tap:setup` as the unified setup/configuration entrypoint.

## Usage

```bash
/tap:setup                # full setup wizard
/tap:setup doctor         # installation diagnostics
/tap:setup mcp            # MCP server configuration
/tap:setup wizard --local # explicit wizard path
```

## Routing

Process the request by the **first argument only** so install/setup questions land on the right flow immediately:

- No argument, `wizard`, `local`, `global`, or `--force` -> route to `/tap:tap-setup` with the same remaining args
- `doctor` -> route to `/tap:tap-doctor` with everything after the `doctor` token
- `mcp` -> route to `/tap:mcp-setup` with everything after the `mcp` token

Examples:

```bash
/tap:setup --local          # => /tap:tap-setup --local
/tap:setup doctor --json    # => /tap:tap-doctor --json
/tap:setup mcp github       # => /tap:mcp-setup github
```

## Notes

- `/tap:tap-setup`, `/tap:tap-doctor`, and `/tap:mcp-setup` remain valid compatibility entrypoints.
- Prefer `/tap:setup` in new documentation and user guidance.

Task: {{ARGUMENTS}}