speckit-check
Run `specify check` to verify that Spec Kit required tools (git, claude, gemini, code, cursor-agent, windsurf, qwen, opencode, codex, shai, qoder, etc.) are installed and available; interpret results and suggest next steps. Use when the user says "check Spec Kit environment", "specify not working", or "slash commands not showing".
Best use case
speckit-check is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Run `specify check` to verify that Spec Kit required tools (git, claude, gemini, code, cursor-agent, windsurf, qwen, opencode, codex, shai, qoder, etc.) are installed and available; interpret results and suggest next steps. Use when the user says "check Spec Kit environment", "specify not working", or "slash commands not showing".
Run `specify check` to verify that Spec Kit required tools (git, claude, gemini, code, cursor-agent, windsurf, qwen, opencode, codex, shai, qoder, etc.) are installed and available; interpret results and suggest next steps. Use when the user says "check Spec Kit environment", "specify not working", or "slash commands not showing".
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "speckit-check" skill to help with this workflow task. Context: Run `specify check` to verify that Spec Kit required tools (git, claude, gemini, code, cursor-agent, windsurf, qwen, opencode, codex, shai, qoder, etc.) are installed and available; interpret results and suggest next steps. Use when the user says "check Spec Kit environment", "specify not working", or "slash commands not showing".
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/speckit-check/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How speckit-check Compares
| Feature / Agent | speckit-check | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run `specify check` to verify that Spec Kit required tools (git, claude, gemini, code, cursor-agent, windsurf, qwen, opencode, codex, shai, qoder, etc.) are installed and available; interpret results and suggest next steps. Use when the user says "check Spec Kit environment", "specify not working", or "slash commands not showing".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Spec Kit Check Skill Run **specify check** to verify that the Spec Kit CLI and required tools (git, AI agents, editors) are installed and detectable. Use this after **speckit-install** or **speckit-initial** to confirm the environment, or when the user reports that slash commands are missing or `specify` does not work. ## When to Use - After initializing a project with **speckit-initial** to confirm the environment. - When slash commands do not appear or the user says "specify not working". - In CI or scripts to ensure dependencies are present before running Spec Kit steps. ## Prerequisites - **Specify CLI** must be installed (see **speckit-install**). If `specify` is not in PATH, direct the user to **speckit-install** before running `specify check`. ## Workflow 1. **Ensure CLI is available** - If the user has not installed the CLI or reports "specify: command not found", direct them to **speckit-install** first. Do not run `specify check` until `specify` is available. 2. **Run the check** - From the project root (or target directory): `specify check` - The command reports which tools are detected (e.g. git, claude, gemini, code, cursor-agent, windsurf, qwen, opencode, codex, shai, qoder) and which are missing or not in PATH. 3. **Interpret the output** - **All required tools present**: Environment is ready; suggest proceeding with **speckit-constitution** or **speckit-specify**. - **CLI missing**: Direct to **speckit-install**. - **Agent or editor missing**: Suggest installing the corresponding Agent/editor or adding its executable to PATH. If the user only needs templates and `.specify/` (no slash commands), suggest re-running **speckit-initial** with `--ignore-agent-tools`. 4. **Summarize and recommend** - Provide a short summary: what is OK, what is missing. - Give concrete next steps: install CLI (**speckit-install**), re-init with different agent (**speckit-initial**), or fix PATH / install Agent. ## Outputs - **Summary**: Which tools are detected and which are missing. - **Recommendations**: List of next actions (install CLI, run init, install Agent, add to PATH, or use `specify init --ignore-agent-tools`). ## Next Steps - If something is missing: use **speckit-install** (for CLI) or **speckit-initial** (to re-init or use `--ignore-agent-tools`), or install the missing Agent/editor. - If check passes: proceed with **speckit-constitution** or **speckit-specify**. ## Example Output (reference) See `examples/sample-output.md` for an example of `specify check` output and how to interpret it. ## Troubleshooting - **"specify: command not found"**: Use **speckit-install**. - **Agent reported as missing**: Ensure the Agent app is installed and its CLI or executable is on PATH; or use `specify init --ignore-agent-tools` if only templates are needed. - **Git missing**: Install git or run `specify init --no-git` if git is not required for the workflow. ## References - [GitHub spec-kit](https://github.com/github/spec-kit) — CLI: specify check
Related Skills
speckit-taskstoissues
Convert tasks.md entries into GitHub issues in the matching remote repository using gh issue create, preserving task IDs for traceability. Use when the user wants to create GitHub issues from an existing tasks.md, needs issue tracking for implementation tasks, or wants to sync task progress with GitHub project boards.
speckit-tasks
Generate a dependency-ordered tasks.md organized by user story, with phased execution (Setup, Foundational, User Stories, Polish), parallel markers, and strict checklist format (checkbox, TaskID, Story label, file path). Use when the implementation plan is ready and the user needs an executable task breakdown before coding.
speckit-specify
Create or update a feature specification from a natural language description by generating a branch, filling the spec template with user stories, functional requirements, success criteria, and running quality validation. Use when the user provides a feature idea and needs a structured, technology-agnostic spec ready for planning.
speckit-plan
Generate a technical implementation plan from a feature spec by filling the plan template, resolving unknowns via research, producing data-model.md, API contracts, and quickstart.md artifacts. Use when the feature spec is ready and the user needs architecture decisions, data models, API schemas, or a structured plan before task generation.
speckit-install
Install the Specify CLI on the host machine (uv tool install or uvx one-time); supports multiple OS, persistent or one-time install, and corporate or restricted-network environments. Use when the user says "install Spec Kit", "install Specify CLI", or "specify command not found".
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".
speckit-implement
Execute the implementation plan by processing tasks from tasks.md phase-by-phase, following TDD order, respecting task dependencies and parallel markers, setting up ignore files, and marking completed tasks. Use when the plan and tasks are ready and the user wants to begin coding, or when resuming implementation after a pause.
speckit-constitution
Create or update the project constitution at .specify/memory/constitution.md by collecting governance principles, filling template placeholders, versioning with semver, and propagating changes to dependent templates and agent config files. Use when setting up initial project governance, amending principles, or syncing constitution changes across spec/plan/tasks templates.
speckit-clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
speckit-checklist
Generate a requirements-quality checklist ('unit tests for English') that validates completeness, clarity, consistency, and measurability of spec/plan/tasks artifacts. Use when the user needs a quality gate before implementation, wants to audit requirement coverage, or needs domain-specific checklists (UX, API, security, performance).
speckit-analyze
Perform a read-only cross-artifact consistency analysis across spec.md, plan.md, and tasks.md, detecting duplications, ambiguities, coverage gaps, and constitution violations with severity ratings. Use when the user has all three artifacts and needs a quality check before implementation, or wants to identify inconsistencies across specifications.
tui-checkbox
Generate and render a pixel-precise ASCII TUI Checkbox component with complete output blocks (TUI_RENDER, COMPONENT_SPEC, PENCIL_SPEC, PENCIL_BATCH_DESIGN) for Pencil MCP drawing workflows. Use when the user asks to create a checkbox in a terminal UI, text-based interface, or Pencil MCP project.