speckit-scaffold-speclisted

Use this skill when the user wants to set up, scaffold, bootstrap, prep, initialize, or prepare a SPEC-ID from the technical roadmap for autonomous execution. Triggers on: set up SPEC-XXX, scaffold SPEC-XXX, bootstrap SPEC-XXX for development, prep SPEC-XXX, initialize the workspace for SPEC-XXX, prepare SPEC-XXX for the autonomous run, create a spec branch and workflow for SPEC-XXX, generate the workflow file for SPEC-XXX, I need a workflow file generated for SPEC-XXX, fill the prompts from the roadmap, pre-fill the workflow template, start working on SPEC-XXX, populate the workflow file for SPEC-XXX. Opens with a blind-spot pass, creates the git worktree, spec branch, Design Concept doc, and populated workflow file, then hands off to planning. Strictly interactive — requires a human to answer the grill-me questions. Not for checking roadmap status (use /speckit-pro:speckit-status), running a populated workflow (use /speckit-pro:speckit-autopilot), or SDD coaching (use /speckit-pro:speckit-coach).
racecraft-lab/racecraft-plugins-public · ★ 5 · AI & Automation · score 74

Install: claude install-skill racecraft-lab/racecraft-plugins-public

# SpecKit Scaffold Spec ## 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. ## Capability discovery & grounding Before researching or recommending, enumerate the tools and skills your session actually exposes — do not assume a fixed set; the user may have installed anything — and select the best fit per `${CLAUDE_PLUGIN_ROOT}/skills/speckit-autopilot/references/capability-discovery.md`. Ground every external fact you assert in a real tool, skill, or file result per `${CLAUDE_PLUGIN_ROOT}/skills/speckit-autopilot/references/grounding.md`, and abstain when nothing grounds it. ## Artifact tiering (CONTRACT vs EXHAUST) speckit-pro artifacts are tiered. **CONTRACT** artifacts (`spec.md`, `plan.md`, `tasks.md`, `research.md`, supporting design artifacts) are review-visible and live at their normal locations. The three authored **EXHAUST** artifacts (the design-concept doc, the workflow file, and the UAT runbook) are scaffolding, so they are written under a `.process/` directory: the design-concept doc and workflow file land under `docs/ai/specs/.process/`, and the UAT runbook lands under the feature's own `specs/<NNN>/.process/`. EXHAUST arti