Skip to main content
By the end of this page you will have done the four things that matter for a real first run:
  1. installed the workflow pack
  2. launched a workflow
  3. inspected the resulting run
  4. chosen whether to go deeper on CLI operations or JSX authoring

​
1. Scaffold the Workflow Pack

bunx smithers-orchestrator init
That creates a local .smithers/ directory with seeded workflows, shared prompts, reusable components, and agent configuration.

​
2. Launch a Seeded Workflow

bunx smithers-orchestrator workflow run implement --prompt "Add rate limiting to the API"
This runs the seeded implement workflow that init installs into .smithers/workflows/. It is the fastest way to see Smithers behave like a workflow runtime instead of a library on a shelf.

​
3. Inspect the Run

Once the workflow starts, use the CLI to see what happened: 
bunx smithers-orchestrator ps
bunx smithers-orchestrator inspect <run-id>
bunx smithers-orchestrator logs <run-id> --tail 20 --follow false
Use ps to find the run ID if you do not already have it.

​
4. Understand What You Just Used

Every workflow gets: You just used both Smithers surfaces together:
  • the workflow pack gave you runnable workflows
  • the CLI launched, inspected, and reported on the run

​
Next Steps