> ## Documentation Index
> Fetch the complete documentation index at: https://smithers-feat-claude-workflow-mirror.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Starters

> Choose a plain-English outcome and the command your agent runs for it.

Smithers ships with starter workflows for when you want a result before your agent writes any workflow code. The commands on this page are what the coding agent runs: a human picks the outcome and asks their agent (or names the starter); the agent runs the matching command. Reading this as an agent? Run them yourself; never hand them to the human. Browse the starter gallery from any repo:

```bash theme={null}
bunx smithers-orchestrator starters
```

First-time setup:

```bash theme={null}
bunx smithers-orchestrator init --add-agents
```

Or initialize with guided next steps for one template:

```bash theme={null}
bunx smithers-orchestrator init --template idea-to-tickets
```

Template IDs:

Pass any ID from this table to `init --template <id>` to scaffold that starter.

| Starter                  | Best for                                   | Workflow                  | Command                                                             |
| ------------------------ | ------------------------------------------ | ------------------------- | ------------------------------------------------------------------- |
| `idea-to-tickets`        | founders, product, operations, engineering | `tickets-create`          | `bunx smithers-orchestrator init --template idea-to-tickets`        |
| `launch-checklist`       | launch owners and operators                | `plan`                    | `bunx smithers-orchestrator init --template launch-checklist`       |
| `customer-incident`      | support escalations                        | `debug`                   | `bunx smithers-orchestrator init --template customer-incident`      |
| `nontechnical-research`  | before-build decisions                     | `research`                | `bunx smithers-orchestrator init --template nontechnical-research`  |
| `requirements-interview` | vague stakeholder requests                 | `grill-me`                | `bunx smithers-orchestrator init --template requirements-interview` |
| `quality-audit`          | release readiness                          | `audit`                   | `bunx smithers-orchestrator init --template quality-audit`          |
| `test-coverage`          | regression prevention                      | `improve-test-coverage`   | `bunx smithers-orchestrator init --template test-coverage`          |
| `ship-a-change`          | focused product improvements               | `research-plan-implement` | `bunx smithers-orchestrator init --template ship-a-change`          |
| `mission-mode`           | larger approved milestones                 | `mission`                 | `bunx smithers-orchestrator init --template mission-mode`           |

Each detailed starter prints:

* What outcome to expect
* What context to gather before running
* The exact `bunx smithers-orchestrator workflow run ...` command
* Useful follow-up commands
* When not to use that starter

Filter by audience or goal:

```bash theme={null}
bunx smithers-orchestrator starters --audience product
bunx smithers-orchestrator starters --goal quality
bunx smithers-orchestrator starters --workflow debug
```

Use JSON when another tool needs the catalog:

```bash theme={null}
bunx smithers-orchestrator starters --format json
```