Skip to Content
TutorialsOverview

Tutorials

Each tutorial is one task, done from start to finish on your own machine. You type the commands, check that you see what the tutorial shows, and end with something real: a merged PR, a cleared queue, a running app. The guides explain every option; the tutorials link to them instead of repeating them.

TutorialYou’ll end up withTime
From zero to a merged PRShep installed, an agent set up, and your first feature merged through a pull request15 min
Run ten features without chaosTen features queued behind a parallel limit, triaged, approved in a batch, retried and paused15 min
Gates, decisions and checkpointsA spec-driven feature you steered at each gate, with a diff and a rollback of its steps15 min
A terminal-only workflow with tmuxshep tui in tmux with log and shell panes, a status-line segment and shep ps10 min
Start an app, then add featuresA new app built from a description, running on a dev server, with a second feature on top15 min

Times are for your own steps. How long the agent takes depends on the task, your agent and your model.

Before you start

Every tutorial assumes the prerequisites from Getting Started:

  • Node.js 22 or newer, and Git.
  • The GitHub CLI gh, signed in with gh auth login.
  • An agent Shep can drive, already signed in: a CLI such as claude, codex, gemini, cursor-agent or copilot, an OpenRouter or Together AI key, or a local Ollama or LLM proxy.

Use a repository where a draft pull request is harmless, such as a personal playground repo. To try the flow without any agent account, pick Demo as your agent: it returns scripted results, so nothing it writes is meant to be merged.

Prefer zero install? app.shep.bot  runs Shep in your browser.

Conventions

  • <id> is a feature id. Shep prints it when you create a feature, and shep feat ls lists them. You can type the first few characters instead of the whole id, as long as they match only one feature.
  • You should see blocks describe the output to check before you move on. Your ids, names and timings will differ.
  • Commands run in your repository’s folder unless a step says otherwise.