GitHub logo

Skill

speckit-init

scaffold Spec Kit projects for Copilot

Published by GitHub Updated Jul 24
Covers Copilot GitHub CLI Engineering

Description

Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running `specify init --integration copilot --integration-options="--skills"`. USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO NOT USE FOR: managing extensions/presets/bundles of an already-initialized project (use the speckit-extension / speckit-preset / speckit-bundle skills instead).

SKILL.md

Spec Kit — init

Initialize a spec-driven development project for GitHub Copilot with the Specify CLI (specify). This skill exposes the specify init command. You (the agent) run the CLI on the user's behalf via the shell; the CLI does the scaffolding.

Because this is the Copilot plugin, always scaffold Copilot in skills mode:

--integration copilot --integration-options="--skills"

This installs spec-kit commands (and any extensions added later) as Copilot Agent Skills.github/skills/speckit-<cmd>/SKILL.md — rather than the default .github/agents/*.agent.md layout. Skills are what Copilot CLI discovers as SKILL.md, so this keeps the project consistent with how this plugin works. Do not omit --integration-options="--skills".

Prerequisite

This skill needs the specify CLI. Confirm it is available:

specify --version

If it is missing (command not found), use the speckit-cli-setup skill to install it first, then continue.

When to use

  • The user wants to start a new spec-kit project.
  • The user wants to add spec-driven development to the current directory.

How to invoke

specify init scaffolds templates, scripts, the spec-kit workflow, shared infrastructure, and the Copilot command files. It runs offline from assets bundled in the installed CLI.

Common forms (always Copilot + skills mode):

# New project directory
specify init <project-name> --integration copilot --integration-options="--skills"

# Initialize in the current directory
specify init . --integration copilot --integration-options="--skills"
specify init --here --integration copilot --integration-options="--skills"

# Current directory is non-empty: skip the confirmation prompt
specify init --here --integration copilot --integration-options="--skills" --force

# Install a preset at init time
specify init <project-name> --integration copilot --integration-options="--skills" --preset healthcare-compliance

Key options

  • --integration copilot — always use this in the Copilot plugin.
  • --integration-options="--skills"required; scaffolds spec-kit commands as Copilot Agent Skills (SKILL.md) instead of .agent.md files.
  • --here / . — initialize in the current directory instead of creating a new one.
  • --force — skip the confirmation when --here targets a non-empty directory.
  • --preset <id> — install a preset during initialization.
  • --script <sh|ps> — choose the helper script flavor.
  • --ignore-agent-tools — skip checks for the agent's CLI tools.

Notes

  • Prefer non-interactive flags so the command does not block on prompts.
  • Always pass both --integration copilot and --integration-options="--skills"; the skills layout is what makes spec-kit commands (and later-added extensions) show up as SKILL.md for Copilot.
  • After init, point the user at the generated skills under .github/skills/ and the .specify/ directory. Newly generated skills are picked up in the current Copilot session with /skills reload, and automatically on the next session start. Suggest specify check to verify their environment.

© 2026 YourAI.tools. Every skill from an identity-verified publisher.

Independent catalog. Not affiliated with, endorsed by, or sponsored by Anthropic or any listed publisher. All trademarks belong to their respective owners.