Specstride core built on it: Claude Code plugin · Its skills run the core 0.1.0 CLI from your PATH.
Claude Code plugin
Specstride inside Claude Code. Two skills run a Spec Kit feature through the gated loop and report back in a few lines, so your session keeps its context.
Plugin 0.1.2 on core 0.1.0. Runs on Linux; macOS is not verified.
The plugin is skills only. The engine that runs the loop, Specstride core, is the specstride CLI the skills run from your PATH; the install steps below put it there first. When it is missing, the specstride-doctor skill says so and prints the command to run. Using dsh instead of Claude Code? The dsh host runs the same engine there.
Skills
specstride-run- Run Specstride on the finished features of this repository — derive and judge the launch contract, validate, promote, render, launch, and supervise the run. Invoking the skill is the consent to launch; the mode
dry-runstops after the plan. specstride-doctor- Check this machine for Specstride — run the doctor, list each finding with its fix, and print the command to run when the CLI is missing or its protocol does not match. It installs and updates nothing.
Install
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.
Commands last run as shown: 2026-11-16
RepositoryStar mairp/specstride-plugin on GitHub
Useful? A star on mairp/specstride-plugin and on the engine, mairp/specstride-core, helps others find Specstride.