Install
Every path below ends with the core's CLI on your machine, so pick the host for your agent; install the core alone only to use the specstride CLI from a shell or to build a host. Each path is one command, curl -fsSL https://specstride.ai/install.sh | bash -s -- <plugin|dsh|hermes|core>, which runs the listed steps in order (add --dry-run to print them first). Commands are run by hand, exactly as written; the date under the path says when it was last verified that way.
Claude Code
Install the engine's CLI, then the plugin in Claude Code, then take the ready-made example feature through its first run before pointing it at your own repository. The plugin is skills only; they run the specstride CLI from your PATH, and nothing is on npm yet, so the CLI is packed from a clone.
Needs
- Linux. macOS is not verified: no Mac has run it.
- Node 22+, git and Claude Code
- A Spec Kit feature: a
specs/NAME/directory with atasks.md, in a git repository (optionally withspec.mdandplan.mdbeside it) - A
testscript inpackage.json - Your own subscription or API key for the models you choose
In one command — runs the steps below, in order (read the script)
curl -fsSL https://specstride.ai/install.sh | bash -s -- plugin
Or step by step
# the engine CLI the plugin's skills run git clone https://github.com/mairp/specstride-core cd specstride-core npm ci # packs the release tarballs into .build/release/ node scripts/pack-release.mjs npm install -g .build/release/specstride-0.1.0.tgz # prints the CLI protocol, 1 specstride --protocol # then the plugin, in Claude Code /plugin marketplace add mairp/specstride-plugin /plugin install specstride@specstride-marketplace # to try it on a ready-made feature first git clone https://github.com/mairp/specstride-example cd specstride-example claude # then say Run Specstride on the feature in this repo.
On your own repository — any git repo with a specs/NAME/tasks.md and a test script in package.json — say the same sentence. Each approved phase becomes its own commit.
Useful? A ★ star on mairp/specstride-plugin helps others find it.
Commands last run as shown: 2026-11-16
dsh
Build the dsh host from a clone, install it with the engine's CLI from the tarball it pins, then put the three skills into your repository. Nothing is on npm yet.
Needs
- Linux. macOS is not verified.
- Node 22+ and git
dsh0.1.0-rc.8 on the search path- A Spec Kit feature in a git repository
In one command — runs the steps below, in order (read the script)
curl -fsSL https://specstride.ai/install.sh | bash -s -- dsh
Or step by step
git clone https://github.com/mairp/specstride-dsh cd specstride-dsh # resolves the pinned engine tarballs; nothing compiles npm install # renders the skills and the shim, runs every build gate npm run build # specstride-host-dsh and the specstride CLI this repository pins npm install -g . vendor/core/specstride-0.1.0.tgz # in your repository; the skills go into .dsh/skills/ specstride-host-dsh install --project # six findings, one line each specstride-host-dsh doctor
Then, in a dsh session in your repository, say "run the specstride-run skill in dry-run on the feature". It plans and validates and launches nothing. Drop "in dry-run" to run the feature for real.
Useful? A ★ star on mairp/specstride-dsh helps others find it.
Commands last run as shown: 2026-11-08
Hermes
Build the Hermes host from a clone, install it with the engine's CLI from the tarball it pins, then put the skills and the plugin into a dedicated Hermes profile. Nothing is on npm yet.
Needs
- Linux. macOS is not verified.
- Node 22+ and git
- Hermes 0.22.2 (the pinned hermes-agent), with a profile
specstride(hermes profile create specstrideif absent) - The engine CLI on PATH or
SPECSTRIDE_BINset - A Spec Kit feature in a git repository
In one command — runs the steps below, in order (read the script)
curl -fsSL https://specstride.ai/install.sh | bash -s -- hermes
Or step by step
git clone https://github.com/mairp/specstride-hermes cd specstride-hermes # resolves the pinned engine tarballs; nothing compiles npm install # renders the skills and the shim, runs every build gate npm run build # specstride-host-hermes and the specstride CLI this repository pins npm install -g . vendor/core/specstride-0.1.0.tgz # skills and plugin into the dedicated profile; run it again → already installed, unchanged specstride-host-hermes install --profile specstride # eight host.* findings, one line each, no model specstride-host-hermes doctor
Then, in a Hermes session on your repository (hermes -p specstride), say "run the specstride-run skill in dry-run on the feature". It plans and validates and launches nothing. Drop "in dry-run" to run the feature for real. Add --with-kanban to the install for the kanban board.
Useful? A ★ star on mairp/specstride-hermes helps others find it.
Commands last run as shown: 2026-11-14
Core (CLI, for host builders)
The dsh and Hermes hosts pin the core, and the Claude Code path above installs its CLI. Install it on its own only to run the specstride CLI from a shell or to build a host on it. Build the engine from a clone and pack its release. Nothing is on npm yet.
Needs
- Linux. macOS is not verified.
- Node 22+ and git
In one command — runs the steps below, in order (read the script)
curl -fsSL https://specstride.ai/install.sh | bash -s -- core
Or step by step
git clone https://github.com/mairp/specstride-core cd specstride-core npm ci # packs the four release tarballs into .build/release/ node scripts/pack-release.mjs npm install -g .build/release/specstride-0.1.0.tgz # prints the CLI protocol, 1 specstride --protocol # in your repository specstride doctor
specstride --help lists every verb. Each verb takes --json, --verbose and -h. To build a host, start from @specstride/host-kit and pass the conformance suite in @specstride/testkit. See the core README.
Useful? A ★ star on mairp/specstride-core helps others find it.
Commands last run as shown: 2026-11-08
After the first run
- Something look off? The
specstride-doctorskill (in Claude Code, dsh or Hermes) checks this machine: it runs the doctor, lists each finding with its fix, and installs nothing. - To end a run cleanly, use the
stopverb of thespecstrideCLI: the run ends at the next safe boundary, the record closes whole, no survivor. - Settings live in your user configuration,
~/.config/specstride/config.yaml— parallel units are turned on there, and with several features inspecs/you setSPECSTRIDE_FEATUREto the directory name. - Every error a run can print, with its fix, is in the wiki's Troubleshooting page.