---
title: Workflow Catalog
description: Canonical workflow packs and marketplace-ready metadata.
---

The default `.smithers` pack is the canonical starting catalog. The pack groups related workflows by purpose. Choose the workflows that match your team's primary use case, or install the full pack and edit it in place. Each entry is normal TSX that can be edited, copied, or published as part of a larger pack.

## Canonical Packs

| Pack | Workflows | Audience |
| --- | --- | --- |
| Build | `hello`, `implement`, `research-plan-implement`, `delegation-chain`, `mission`, `kanban`, `ralph`, `workflow-skill`, `create-workflow`, `create-skill`, `context-engineer`, `route-task`, `smithering`, `make-workflow-tutorial`, `extract-skill`, `vcs` | Teams delegating code changes, authoring durable automations, and routing operator requests. |
| Plan | `research`, `plan`, `ticket-create`, `tickets-create`, `grill-me` | Product, engineering, and operations users turning ambiguous work into scoped tickets. |
| Quality | `review`, `debug`, `improve-test-coverage`, `feature-enum`, `audit`, `context-doctor`, `backpressure-plan`, `triage-run`, `report-slideshow`, `eval-author` | Maintainers who need repeatable review, diagnostics, test hardening, and evidence-backed gates. |
| System | `init`, `post-failure`, `upgrade` | Internal plumbing (hidden from default listings): durable pack install/refresh, automatic failed-run autopsies, and assisted Smithers upgrades. |

## Marketplace Metadata

Workflow packs should document:

- workflow ID and display name
- required agents and tools
- required Gateway scopes
- input schema and example input
- expected outputs
- whether the workflow writes files, opens pull requests, or needs approval
- recommended sandbox runtime
- validation command

Use that metadata in README files, internal catalogs, or hosted pack registries.

## Publishing Checklist

Before sharing a workflow pack:

- Run the workflow on a disposable repository.
- Confirm every write path goes through approval or review when needed.
- Document the operator steps for non-coding teammates.
- Include a small example input and the expected final output.
- Note which failures are safe to retry and which require human intervention.
