bunx smthrs init creates a focused .smithers/workflows/ directory with create-workflow, create-skill, and docs-driven-development; hidden system workflows support init, failure autopsies, and upgrades. The former starter suite lives in examples/init-pack/; monitoring stays smithers monitor and Gateway /monitor.
Run any curated workflow by ID:
--prompt as shorthand for --input '{"prompt":"..."}'; workflows with structured inputs also take --input directly.
Writing your own workflow? Read Workflow Authoring Rules first: five rules (reserved output columns, no nested loops, loop output binding, the renderWorkflow test contract, and .smithers/package.json test registration) that otherwise get learned one runtime failure at a time.
Workflows
Operational Notes
- Curated workflow files are user-owned after scaffold:
bunx smthrs initwon’t overwrite edited files without--force. - Agent pools live in
.smithers/agents.ts; edit it to change which models each workflow uses. - Run
bunx smthrs workflow listfor repo workflows,bunx smthrs workflow inspect WORKFLOW_IDfor metadata and the input schema, andbunx smthrs workflow skillsto generate agent-facing docs under.smithers/skills/. - Workflows can carry optional metadata comments (
smithers-display-name,smithers-description,smithers-tags,smithers-aliases) for display/discovery inworkflow listandworkflow-skill. - Workflows marked
system: true(or// smithers-system: true) are internal plumbing for Smithers’ own durable processes (e.g. the seededinitworkflow, which installs/refreshes the pack). They’re hidden by default fromworkflow list, the interactive picker, MCPlist_workflows, and gatewaylistWorkflows; pass--system(CLI),includeSystem: true(MCP), orfilter.includeSystem(gateway RPC) to see them, then run withworkflow run <id>. - Inspect and resume runs with the normal CLI (
inspect,logs,chat,events,why,approve,up --resume), or watch every run live in the browser withbunx smthrs monitor(the Smithers Monitor).