Skip to main content
bunx smithers-orchestrator init creates a .smithers/workflows/ directory with ready-to-run workflows for planning, implementation, review, tickets, audits, and long-running missions. These workflows are normal Smithers TSX files: run them as-is, edit them for your repo, or use them as examples for your own workflow pack. Run any default workflow by ID:
bunx smithers-orchestrator workflow run WORKFLOW_ID --prompt "..."
Most prompt-driven workflows accept --prompt as shorthand for --input '{"prompt":"..."}'. Workflows with structured inputs also support --input.

Workflows

WorkflowUse it for
helloThe smallest possible workflow: a single agent task that runs a Markdown prompt.
implementImplement a change with validation and review.
research-plan-implementResearch, plan, implement, validate, and review in one run.
missionRun long-horizon work as approved milestones with focused workers.
kanbanImplement ticket files from .smithers/tickets/ in worktree branches.
ralphKeep an agent working continuously on a prompt.
workflow-skillCreate or update agent-facing skill docs from local workflows.
create-workflowBuild a new Smithers workflow from a plain-English ask.
create-skillAuthor a new agent skill from a plain-English ask.
context-engineerTurn vague work into a contract, route, backpressure, execution, and report.
route-taskClassify a plain-English script and run or recommend the right durable workflow.
smitheringRoute work by size, from trivial task to full plan-build-validate-deliver pipeline.
extract-skillHarvest reusable skills, workflow sketches, and memory from a run or pattern.
vcsInspect and act on a git or jj working tree.
reviewReview current repo changes with one or more configured agents.
planProduce a practical implementation plan.
researchGather repo and external context before planning or building.
debugReproduce and fix a bug with validation.
improve-test-coverageAdd missing tests and validate coverage-related changes.
ticket-createCreate one structured ticket from a prompt.
tickets-createBreak a request into multiple implementable tickets.
grill-meInterrogate a vague plan until requirements are clearer.
feature-enumBuild or refine a code-backed feature inventory.
auditAudit feature groups for gaps and follow-up work.
context-doctorLint a context contract for missing goals, inputs, verification, approvals, and reports.
backpressure-planTurn acceptance criteria into a gate matrix.
triage-runDiagnose a failed or stuck run and recommend a fix, rewind, retry, or escalation.
report-slideshowGenerate a concise HTML slideshow report from run state and artifacts.
monitor-smithersWatch the Smithers fleet for stuck, blocked, failed, or over-budget runs.
monitorWatch, diagnose, optionally self-fix, and report on one running workflow.
eval-authorTurn acceptance criteria into eval fixtures and a rubric for bunx smithers-orchestrator eval.

Operational Notes

  • Default workflow files are user-owned after scaffold. bunx smithers-orchestrator init will not overwrite edited files unless you pass --force.
  • Agent pools are defined in .smithers/agents.ts; edit that file to change which models each workflow uses.
  • Run bunx smithers-orchestrator workflow list to see the workflows in the current repo, bunx smithers-orchestrator workflow inspect WORKFLOW_ID to see metadata and the workflow input schema, and bunx smithers-orchestrator workflow skills to generate agent-facing docs under .smithers/skills/.
  • Workflows can carry optional metadata comments (smithers-display-name, smithers-description, smithers-tags, smithers-aliases) that bunx smithers-orchestrator workflow list and workflow-skill use for display and discovery.
  • Inspect and resume runs with the normal CLI: inspect, logs, chat, events, why, approve, and up --resume.