Project Initialization
The primary way to configure agent integration is through thespecify init command. This sets up the complete project structure with agent-specific configurations.
Basic Initialization
- New Project
- Existing Project
Create a new project directory with Spec Kit integration:
Agent-Specific Configuration
Each agent has unique configuration requirements based on its directory structure and command format.Claude Code Configuration
Claude Code Configuration
Directory Structure:Initialization:Special Notes:
- Uses Markdown format with
$ARGUMENTSfor argument passing - Supports the
claude migrate-installercommand - CLI tool checked at
~/.claude/local/claudeas fallback
Gemini CLI Configuration
Gemini CLI Configuration
Directory Structure:Initialization:Special Notes:
- Uses TOML format with
{{args}}for argument passing - Requires
geminiCLI tool installation - Commands stored in
promptfield of TOML files
GitHub Copilot Configuration
GitHub Copilot Configuration
Directory Structure:Initialization:Special Notes:
- Uses
.agent.mdextension with specialmodefrontmatter field - IDE-based, no CLI tool requirement
- Commands stored in
.github/agents/(notcommands/subdirectory)
Windsurf Configuration
Windsurf Configuration
Directory Structure:Initialization:Special Notes:
- Uses
workflows/subdirectory instead ofcommands/ - IDE-based, no CLI tool requirement
- Markdown format with
$ARGUMENTS
opencode Configuration
opencode Configuration
Directory Structure:Initialization:Special Notes:
- Uses singular
command/directory (unique to opencode) - Requires
opencodeCLI tool installation - Markdown format with
$ARGUMENTS
Generic Agent Configuration
Generic Agent Configuration
Custom Directory Structure:Initialization:Special Notes:
- Requires
--ai-commands-dirparameter - Creates standard Markdown format commands
- No CLI tool checks performed
- Useful for unsupported or custom agents
Advanced Configuration Options
Script Type Selection
Choose between POSIX shell scripts (bash/zsh) or PowerShell scripts:When to use each:
sh: Linux, macOS, WSL, or bash-compatible environments (default)ps: Windows with PowerShell, cross-platform PowerShell scenarios
Agent Skills Installation
Install commands as agentskills.io compatible skills:- Creates agent-specific
skills/directory (e.g.,.claude/skills/) - Converts each command to a skill with
SKILL.mdfile - Adds enhanced descriptions and metadata
- Enables skill discovery and portability
Git Repository Management
- Automatic Git Init (Default)
- Skip Git Initialization
By default, Spec Kit initializes a Git repository with an initial commit:
Tool Requirement Override
Skip CLI tool checks during initialization:GitHub API Configuration
When working in environments with rate limiting (CI/CD, corporate networks):- Increases rate limit from 60/hour to 5,000/hour
- Required in some corporate/CI environments
- Prevents template download failures
Debug Mode
Enable verbose diagnostic output for troubleshooting:- Detailed API request/response information
- Template extraction progress
- File creation operations
- Error stack traces
Project Structure
Regardless of the agent chosen, all projects share this core structure:Environment Variables
SPECIFY_FEATURE
Override automatic feature detection for non-Git repositories:When to use:
- Working in a repository without Git branches
- Overriding automatic feature directory detection
- Testing or debugging feature workflows
GitHub Authentication
Configure GitHub API access:Multi-Agent Projects
You can initialize a project with multiple agents by runningspecify init multiple times:
Updating Agent Configurations
To update agent configurations after initialization:Reinitialize Project
The
--force flag merges new templates and commands without prompting. Your existing .specify/specs/ and .specify/memory/constitution.md are preserved.Customizing Commands
You can customize the generated slash commands after initialization:- Markdown Commands
- TOML Commands
Edit command files directly in
.claude/commands/, .cursor/commands/, .opencode/command/, etc.Troubleshooting
Commands not appearing in agent
Commands not appearing in agent
Symptoms: Slash commands don’t show up in your AI agentSolutions:
- Restart your AI agent or IDE
- Verify command files exist in the correct directory:
- Check file permissions (especially on Unix systems):
- Ensure you’re in the project root directory
Script execution failures
Script execution failures
Symptoms: Commands fail when trying to execute scriptsSolutions:
- Verify script executable permissions:
- Check script type matches your system:
- Reinitialize with correct script type:
Template download failures
Template download failures
Symptoms: GitHub API rate limit errors during initializationSolutions:
- Use GitHub token for authentication:
- Set environment variable:
- Wait for rate limit to reset (check with
--debugflag)
Agent tool not found
Agent tool not found
Symptoms: CLI tool check fails during initializationSolutions:
- Install the required CLI tool:
- Verify tool is in PATH:
- Use
--ignore-agent-toolsto skip check (if you’ll install later):
Next Steps
Supported Agents
View all 15+ supported AI agents with installation links and status
Agent Overview
Learn about agent integration concepts and the spec-driven workflow
Quick Start Guide
Get started with your first spec-driven development project
CLI Reference
Complete reference for all Specify CLI commands
CLI Reference
Complete reference for all Specify CLI commands and options