speckit-scaffold-speclisted

# SpecKit Setup ## Scope Use this skill when the user wants a SPEC-ID prepared for `$speckit-autopilot`. This skill is responsible for the mutation-heavy bootstrap step: identify the roadmap entry, create or reuse the correct worktree branch, generate the workflow file, and leave the repository in a state where the autopilot can start immediately. If the user is still figuring out how to decompose a feature, write a technical roadmap, or understand the SDD process, redirect them to `$speckit-coach`. Do not invent roadmap data or phase prompts from vague requirements when the roadmap entry does not exist. > **Codex implicit-trigger note (eval harness vs production):** Layer 2 trigger evals score this skill at 69% (11/16) on the Codex selector — but POS is a perfect 8/8 (every "scaffold SPEC-009" / "create a new spec branch" / "prep SPEC-022 for autopilot" 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 ("roadmap status" / "what's the progress on SPEC-009" → should go to `$speckit-status`, "run the fully populated workflow" → `$speckit-autopilot`, "resolve PR review comments" → `$speckit-resolve-pr`). In production all six speckit-pro skills are loaded together and Codex routes those queries to their proper destinations. The eval results under-report real-world accuracy; positive-trigger reliability is the operationally-rele