| layout | default |
|---|---|
| title | Dotdog Spec Kit Extension |
Dotdog imports GitHub Spec Kit feature artifacts into local, queryable knowledge graphs without modifying the source artifacts.
The next extension version is 1.0.0 and is not published yet. Its release archive will be https://github.com/specdog/dotdog/releases/download/v1.0.0/dotdog-spec-kit-extension-v1.0.0.zip. The installation below refers to the existing published 0.9.0 extension until the next release is created.
- GitHub Spec Kit 0.12.0 or newer
- Dotdog 0.9.0 or newer
- A Spec Kit project containing
.specify/andspecs/
Extension compatibility CI uses pinned Spec Kit 0.12.0 and 1.2.5 sources and the installed package's actual version. It verifies archive installation and command files, not agent-host execution. Current-head CI results determine compatibility; a declared minimum alone is not evidence that it passed.
Install Dotdog:
npm install -g [email protected]Install the extension from the versioned release asset:
specify extension add dotdog --from https://github.com/specdog/dotdog/releases/download/v0.9.0/dotdog-spec-kit-extension-v0.9.0.zipThe release also includes a SHA-256 checksum. Verify the downloaded ZIP against dotdog-spec-kit-extension-v0.9.0.zip.sha256 before manual installation or redistribution.
/speckit.dotdog.importimports feature artifacts into.doghouse/speckit/and compiles them./speckit.dotdog.inspectaudits imported graphs and reports model gaps./speckit.dotdog.servestarts Dotdog's local stdio MCP server for the imported graphs.
The commands operate only on the current Spec Kit project root. They reject arbitrary path arguments and do not interpolate user input into shell commands.
The importer is local-only. It does not make network requests, upload source content, or modify .specify/ and specs/. Generated files are hash-tracked, edited outputs are preserved by default, Markdown source is quoted, and symlinked or protected paths are rejected. The MCP command remains attached to stdio and does not expose a network listener.