speckit-installlisted

# SpecKit Install ## Scope Install the official SpecKit CLI (https://github.com/github/spec-kit) if missing, then initialize the current repository for one or both coding-agent integrations (Claude Code, Codex CLI). Safe to run on any repo — detects an existing `.specify/` directory and hands off to `$speckit-upgrade` rather than mutating it. This skill is **mutation-heavy** (it writes files to the repo and to `~/.local/share/uv/tools/specify-cli/` if installing the CLI). It runs only on explicit operator request and never auto-fires from other skills. ## Scope Boundaries — Not For - Upgrading an existing SpecKit install. That is `$speckit-upgrade`. This skill hands off to it automatically when `.specify/` is present. - Scaffolding a new spec from the technical roadmap. That is `$speckit-scaffold-spec`. - Installing this plugin's own bundled Codex subagent TOML files (`autopilot-fast-helper.toml`, `phase-executor.toml`, etc.) into `~/.codex/agents/`. That is `$install`. - Methodology coaching. That is `$speckit-coach`. > **Codex implicit-trigger note (eval harness vs production):** Layer 2 trigger evals score this skill at 75% (15/20) on the Codex selector — but POS is a perfect 10/10 (every "install speckit" / "set up speckit" / "$speckit-install" query fires correctly). All 5 NEG misses are false-positives in single-skill staging where the harness loads only this skill, so the Codex selector has no alternative to route adjacent SDD queries to ("status of SPE