speckit-installlisted
Install: claude install-skill racecraft-lab/racecraft-plugins-public
# SpecKit Install
## Installed Runtime Contract
Installed Claude and Codex surfaces resolve Python 3.11 or newer, invoke
`[resolved_python, "-m", "speckit_pro_runner"]`, send one JSON request on
stdin, read one JSON response from stdout, and surface stderr diagnostics.
Do not add a shell fallback, `jq` parsing path, Git Bash, WSL, or
PowerShell-specific command-language requirement for installed workflows.
## Invocation
```text
/speckit-pro:speckit-install # interactive — asks which integrations
/speckit-pro:speckit-install claude # claude only
/speckit-pro:speckit-install codex # codex only
/speckit-pro:speckit-install claude codex # both (dual-integration)
```
## What to Do
### 1. Ensure the SpecKit CLI is on PATH
Use command execution to check whether `specify --version` succeeds after
including common user-local binary directories on PATH.
- If the output begins with `specify`, the CLI is installed. Capture the
version and move on.
- If the CLI is missing:
- Check whether `uv` is available.
- If `uv` is present, install with `uv tool install specify-cli --from git+https://github.com/github/spec-kit.git`.
- If `uv` is missing, STOP and instruct the operator to install `uv`
from the official Astral documentation, then re-run
`/speckit-pro:speckit-install`.
### 2. Detect existing-install state
Inspect whether `.specify/` exists and record the state as `PRESENT` or
`ABSENT`.
If `.specify/` is **PRESE