.smithers pack is the canonical starting catalog. Each pack groups related workflows by purpose. Choose the pack that matches your team’s primary use case, or install all three. Each entry is normal TSX that can be edited, copied, or published as part of a larger pack.
Canonical Packs
| Pack | Workflows | Audience |
|---|---|---|
| Build | implement, research-plan-implement, mission, kanban, ralph | Teams delegating code changes to long-running agents. |
| 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 | Maintainers who need repeatable review, diagnostics, and test hardening. |
| Meta | workflow-skill, create-workflow | Teams generating skill docs from their pack, and authoring new workflows from a plain-English ask. |
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
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.