skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
full-stack-skills/speckit-skills79 installs

speckit-initial

Run `specify init` in the current or target directory to bootstrap a Spec Kit project (pull .specify/ and slash commands); supports multiple AI agents and --script sh/ps. Use when the user says "initialize Spec Kit project", "specify init", or "set up Spec Kit in this repo".

How do I install this agent skill?

npx skills add https://github.com/full-stack-skills/speckit-skills --skill speckit-initial
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill initializes a Spec Kit project by running the specify CLI, which pulls configuration and scripts from a GitHub repository. While the source is a well-known service, the skill creates an indirect prompt injection surface by ingesting external data (memory and specs) that the agent later processes as context for slash commands.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Spec Kit Initial Skill

Run specify init to initialize a Spec Kit project: pull .specify/ (memory, scripts, templates, specs) and register /speckit.* slash commands with the chosen AI Agent. This skill assumes the Specify CLI is already installed; if not, direct the user to speckit-install first.

When to Use

  • First time enabling Spec Kit in a project ("initialize Spec Kit", "set up Spec Kit here").
  • Switching AI Agent (e.g. from Claude to Cursor or Gemini).
  • Initializing in a new or existing directory.
  • Need PowerShell scripts on Windows (--script ps).

Prerequisites

  • Specify CLI installed (see speckit-install). If specify is not in PATH, guide the user to run speckit-install before proceeding.
  • Git (optional; use --no-git if the project is not a git repo or you want to skip git-related setup).

Workflow

  1. Verify CLI

    • If the user reports "specify command not found" or has not installed the CLI, direct them to speckit-install first. Otherwise proceed.
  2. Choose parameters

    • --ai (required for slash commands): claude | cursor-agent | gemini | copilot | windsurf | qwen | opencode | codex | qoder | amp | shai | bob | kilocode | auggie | roo | codebuddy — pick the agent the user will use in this project.
    • --script: sh (default, Bash) or ps (PowerShell). Use ps on Windows when the user needs PowerShell scripts.
    • Target: specify init . or specify init --here for current directory; or specify init <project_name> for a new subdirectory.
    • --force: Overwrite existing .specify/ if present (use with care).
    • --no-git: Skip git-related setup.
    • --ignore-agent-tools: Do not install or check agent-specific tools; only pull templates and .specify/ structure.
    • --github-token or GITHUB_TOKEN: For private repos or rate-limited access.
  3. Run the command

    • Give a concrete command for the user's OS and chosen agent. Examples:
      • Current dir, Cursor: specify init . --ai cursor-agent
      • Current dir, Claude: specify init . --ai claude
      • Windows, Copilot, PowerShell scripts: specify init . --ai copilot --script ps
      • New subdir: specify init my-app --ai gemini
  4. Confirm outputs

    • After success: project contains .specify/ (memory, scripts, templates, specs) and the Agent has /speckit.* slash commands available.

Outputs

  • Project: .specify/ directory with memory, scripts, templates, and specs.
  • Agent: Slash commands (e.g. /speckit.constitution, /speckit.specify, /speckit.plan) available in the chosen AI Agent.

Next Steps

  • Run speckit-check to verify the environment (optional but recommended).
  • Then use speckit-constitution or speckit-specify to start the Spec Kit workflow.

Different Environments

EnvironmentExample
Linux / macOS, Cursorspecify init . --ai cursor-agent
Linux / macOS, Claudespecify init . --ai claude
Windows, Copilot, PowerShellspecify init . --ai copilot --script ps
New subdirectoryspecify init my-project --ai gemini
Overwrite existing .specifyspecify init . --ai claude --force
No gitspecify init . --ai claude --no-git
Templates only (no agent tools)specify init . --ai claude --ignore-agent-tools

Troubleshooting

  • "specify: command not found": Use speckit-install first.
  • Windows slash commands not appearing: Ensure you used --script ps if the agent expects PowerShell, and that the agent is configured to load commands from the project.
  • Private repo / rate limit: Set GITHUB_TOKEN or pass --github-token <token> as documented by spec-kit.

References

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/full-stack-skills/speckit-skills/speckit-initial">View speckit-initial on skillZs</a>