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".

16 stars

Best use case

speckit-check is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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".

Teams using speckit-check should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/speckit-check/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/tools/speckit-check/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/speckit-check/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How speckit-check Compares

Feature / Agentspeckit-checkStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/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.

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

tpscheck-automation

16
from diegosouzapw/awesome-omni-skill

Automate Tpscheck tasks via Rube MCP (Composio). Always search tools first for current schemas.

safety-checker

16
from diegosouzapw/awesome-omni-skill

Identifies unsafe operations in Zig code including pointer casts, bounds checking, null pointer dereferences, and undefined behavior. Use when writing low-level code, reviewing safety-critical sections, or debugging crashes.

identitycheck-automation

16
from diegosouzapw/awesome-omni-skill

Automate Identitycheck tasks via Rube MCP (Composio). Always search tools first for current schemas.

check-duplicates

16
from diegosouzapw/awesome-omni-skill

Check for duplicate or similar cases. Use before deep analysis to avoid investigating the same incident twice. Takes a CASE_ID and returns list of similar cases.

aget-check-evolution

16
from diegosouzapw/awesome-omni-skill

Monitor .aget/evolution/ directory health. Validates file counts, naming conventions, disk usage, and returns health status with alerts on anomalies.

add-check

16
from diegosouzapw/awesome-omni-skill

Add a new code quality check to CI, justfile, and pre-commit hooks. Use when adding linters, formatters, type checkers, or other code quality tools to the project.

security-validation-checklist

16
from diegosouzapw/awesome-omni-skill

Guides security validation checklist: Signal protocol security, encryption standards, authentication patterns, data protection. Use when validating security, reviewing security implementations, or ensuring security compliance.

security-compliance-compliance-check

16
from diegosouzapw/awesome-omni-skill

You are a compliance expert specializing in regulatory requirements for software systems including GDPR, HIPAA, SOC2, PCI-DSS, and other industry standards. Perform compliance audits and provide im...

security-checklist

16
from diegosouzapw/awesome-omni-skill

Analyze a security checklist Excel file by interactively identifying the relevant sheet, countermeasure entries, and output column, then checking whether GitHub Enterprise supports each item using the customer-security-trust FAQ and past reference checklists.

Pentest Checklist

16
from diegosouzapw/awesome-omni-skill

This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.

owasp-mobile-security-checker

16
from diegosouzapw/awesome-omni-skill

Analyze Flutter and mobile applications for OWASP Mobile Top 10 (2024) security compliance. Use this skill when performing security audits, vulnerability assessments, or compliance checks on mobile applications. Performs automated scans for hardcoded secrets, insecure storage, weak cryptography, network security issues, and provides detailed remediation guidance.

Dependency Health Check

16
from diegosouzapw/awesome-omni-skill

Assess dependency health across CVE exposure, freshness, maintainer risk, and license compatibility