Docs

The documentation lives next to the code, so it changes when the code does. These links go to it on GitHub.

Start here

  • Getting started

    Install, the shape of a feature, and the sentence that starts a run.

  • Example repository

    A tiny Node project with one three-phase Spec Kit feature to try Specstride on, with a demo of a real run.

  • How it works

    What happens in each phase — the implementer, the engine's verification, the reviewer, the approval and the rejection — plus the parallel-units layer.

The Claude Code plugin

  • Plugin README

    Install, how it works, parallel units, requirements and costs.

  • Wiki home

    The index of the wiki: getting started, how it works, costs and limits, troubleshooting, FAQ.

  • Costs and limits

    The model and parallel-units variables with their defaults, and what each attempt costs.

  • Troubleshooting

    The errors a run prints, each with its fix. Start with the specstride-doctor skill.

  • FAQ

    Which model to use, whether your code goes anywhere new, keys, and who makes it.

The engine

  • Core README

    Loop engineering and governance, the L0–L7 layering, the packages, and how to build and test the engine.

  • Parallel units

    How to switch the option on, when it falls back to running in order, and what it does and does not promise.

  • Publishing the core

    How the four release packages are packed and versioned, and how a host pins a core release by its tarballs and sha256.

  • Security

    Report vulnerabilities privately, and read the known limits: the implementer runs with your permissions.

The other hosts

  • dsh host README

    Install, the doctor's six findings, a walkthrough from dry run to supervised run, what the host writes and where, and troubleshooting.

  • Hermes host README

    The quickstart, the doctor's eight findings, push notices to Telegram, and the kanban board as an install option.

  • Contributing

    Build, typecheck, test, and an end-to-end run that needs no account; add a test with each change.

Questions and bugs go to issues.